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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds behavioral details beyond annotations: 'newest first' ordering, return structure ({ total, page, limit, count, responses: [...] }), and pagination semantics. This is meaningful additional transparency without repeating annotation content.

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?

The description is compact and well-structured: a one-sentence purpose, a clear args block, a returns line, and a routing note. Every sentence adds value—no fluff or redundancy. The most critical scoping (newest first, alternatives) is front-loaded.

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 paginated list tool with no output schema, the description covers everything an agent needs: parameter meanings, default/constraint values, return shape, ordering, and alternatives. Combined with comprehensive annotations, nothing is missing for correct invocation.

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 50% (only form_id and response_format have descriptions). The description fully compensates by explaining all four parameters: form_id (the form's ID), page (1-based, default 1), limit (page size 1-100, default 20), and response_format ('markdown'|'json'). It adds clarity beyond the schema, especially for page and limit which lack schema descriptions.

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?

The description states a specific action ('List submitted responses'), a clear resource ('for a form'), and an ordering ('newest first'). It clearly distinguishes from siblings like foxform_get_response (single response), foxform_export_responses (full dump), and foxform_get_form_analytics (aggregate metrics) without ambiguity.

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?

Explicitly names alternatives and when to use them: 'For aggregate metrics use foxform_get_form_analytics; for a full dump use foxform_export_responses.' This provides direct guidance on when not to use this tool, leaving nothing to inference.

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