Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, so safety is covered. The description goes further by disclosing the returned field set (valuable since there is no output schema), the source (Entry Manager), and the underlying endpoint (GET /forms/{identifier}/comments.json), adding real context beyond the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then packs field list, optional filter, pagination, and endpoint into a tight, waste-free block. Every fragment contributes information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with 100% schema coverage and a readOnly annotation, listing the returned fields compensates for the absent output schema, and pagination plus the optional filter are covered. Only minor behavioral detail (e.g., default page size context) is left implicit in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents form, entryId, pageSize, and pageStart fully. The description's mentions of 'Optionally only for one entry' and pagination largely restate the schema, warranting the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List the comments team members left on a form's entries') and enumerates the returned fields (CommentId, EntryId, Text, CommentedBy, DateCreated), which cleanly separates it from sibling tools like wufoo_list_form_entries and wufoo_count_form_comments.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It notes the optional single-entry narrowing ('Optionally only for one entry'), which implies a valid usage mode, but never tells the agent when to pick this over wufoo_count_form_comments or wufoo_list_form_entries. Usage is inferable but no explicit when/when-not or alternative routing is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.