List form responses

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the 'Read-only' clause largely repeats structured data. The added value is the 'completed or in-progress' characterization of status states. No pagination, auth, or scope behavior is disclosed beyond annotations.

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?

One compact sentence with the resource and scope front-loaded and no filler. It is appropriately sized for a simple read tool, though the trailing 'Read-only' clause duplicates annotations and earns little.

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 full schema coverage and complete annotations but no output schema, the description conveys what is listed and its linkage context. It could note automatic all-page fetching or filter combinations, but nothing essential to invocation is missing.

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 all six parameters (page, per_page, status, subject_id, subject_type, template_id) are already documented in the schema. The description adds no filter syntax or semantics beyond that, so the baseline 3 applies.

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 (List) and resource (form responses) and clarifies what a form response is with 'completed or in-progress fill-outs of a form, attached to a work order or PM.' It distinguishes from list_form_response_answers implicitly by describing whole responses, but never names a sibling to route against.

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?

The phrase 'attached to a work order or PM' gives context about what responses are linked to, but there is no explicit when-to-use, when-not-to-use, or alternative naming (e.g., list_form_response_answers, get_form_response). Guidance is absent.

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