Get form responses

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'List responses submitted to a form,' which is a simple read operation that is already evident from the name. It does not disclose pagination, default page size, ordering, or the format of returned data, leaving significant ambiguities.

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, direct sentence with no filler. It is front-loaded with the action and object, making it easy to parse. Every word earns its place, exemplifying conciseness.

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?

Without an output schema or annotations, the description should explain what the response list includes, any pagination behavior, and ordering. It provides none of this context, leaving a 3-parameter tool under-specified for an agent to invoke confidently.

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?

The schema has 100% description coverage for all three parameters (formId, account, pageSize), so the baseline is 3. The description adds no extra semantic detail beyond what the schema already provides, making it adequate but not enhanced.

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 'List responses submitted to a form' uses a specific verb (List) and resource (responses submitted to a form), clearly indicating the tool's function. It is distinguishable from sibling tools like google_forms_get, which likely retrieves form metadata. However, it does not specify what aspects of responses are included, so it is not maximally specific.

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 gives no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as requiring a form ID, or when to prefer this over google_forms_get. No context or exclusions are provided, leaving the agent to infer usage from the name alone.

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