list_responses

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

With no annotations, the description entirely fails to disclose behavioral traits. It does not state that the operation is read-only, whether authentication is required, the format of the response (e.g., array of objects), or any pagination or rate limits. The description only says 'list responses', offering minimal transparency.

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 a single sentence with 5 words, making it concise. However, it is too terse to be useful; important details are omitted. While front-loaded with the verb 'List', it fails to provide sufficient information to justify its brevity.

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?

Given the tool's simplicity (one parameter, no annotations, but an output schema exists), the description is incomplete. It does not describe how to use the parameter, what the response looks like, or any constraints. The output schema might cover return values, but the description does not leverage it.

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 0%, so the description must add meaning beyond the schema. The sole parameter 'form_id' is not explained at all – no hint about how to obtain it, its format, or its role. The description adds zero value for understanding the parameter.

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 the verb 'List' and the resource 'submitted responses for a form', indicating the tool returns multiple responses for a given form. It implicitly distinguishes from the sibling 'get_response' (singular) but does not explicitly mention the scope (e.g., all responses) or output format.

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 provides no guidance on when to use this tool versus alternatives like 'get_response' or 'get_form'. It does not specify prerequisites, such as the form existing or user permissions, nor any scenarios where this tool is preferred.

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