List Form Responses

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior, so the description adds no new behavioral context. It does not mention pagination behavior, response ordering, or any other trait beyond what annotations and schema already provide.

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 one short, front-loaded sentence with no filler or unnecessary detail. It is concise, though it largely restates the title and provides no additional structural information.

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 simple list operation with a full output schema, rich annotations, and complete parameter documentation, the description is sufficient to call the tool correctly. The main gap is usage guidance relative to sibling tools, which is already accounted for in that dimension.

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?

All four parameters are fully described in the input schema (100% coverage), so no compensation is needed from the description. The description itself adds no parameter-level meaning, which is acceptable given the complete schema.

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 verb ('List') and resource ('a form's responses'), making the operation clear. It does not explicitly mention sibling tools like get_form_response, so the agent must infer the collection-versus-single distinction from the plural noun and tool name.

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 description is a single clause with no guidance on when to use this tool versus alternatives such as get_form_response or get_form. There are no stated conditions, exclusions, or routing hints for the agent.

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