get_form_responses

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

The description adds pagination details (limit of 20 per page) and ordering (most recent first) beyond annotations, which already indicate read-only and idempotent. No contradictions with 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?

The description is concise, consisting of a header and two clear sentences. It is front-loaded with the purpose and provides necessary details without fluff.

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 tool with no output schema, the description covers purpose, ordering, and pagination. However, it lacks details on what a response contains and error conditions, which could be helpful for an AI agent.

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 covers all 4 parameters with descriptions, so baseline is 3. Description adds context about pagination but does not elaborate on parameter usage beyond schema. Slight inconsistency: description mentions 'a user' but users parameter supports multiple.

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 clearly states it retrieves form responses, specifying the action and resource. However, it does not differentiate from sibling tool 'get_assessment_responses' which might serve a similar purpose.

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?

No explicit guidance on when to use this tool versus alternatives like get_assessment_responses. The description implies it is for form responses but does not provide usage context or exclusions.

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