I'd prefer to keep it compact and terse, on two lines called Input: and Output: (note that POD needs a blank line between them). If two lines aren't enough then use one line per variable

I also like to write the POD for a function above the function - not at the end of the file. This is slightly awkward to do with POD though (all those blank lines around the =cut etc), but it looks like this :- 

############################################################

=item daft_function()

This is a daft function.  Write general stuff about it here.

Input:  @daft, [ $DEBUG ]

Output: { FAILED => <0|1>, ANSWER => <string> }

or maybe if you want a bit more description

Input:
        @daft - array of useless items
        $DEBUG - optional paramter to give daft verbiage
    
Output:
        Reference to an anonymous hash with these keys
            FAILED => 0 or 1
            ANSWER => string - result of dafting the input 

=cut

############################################################

sub daft_function
{
    my ($self, @daft) = @_;
    #...
    return $result;
}

[download]
I haven't been using POD for very long though so maybe others have some more POD specific ideas?

In reply to Re: Recommended subroutine documentation style by ncw
in thread Recommended subroutine documentation style by markjugg

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.