List form submissions

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, covering the safety profile. The description adds the quota/proxy caveat ('every page counts against the API quota') and mentions community data, but omits pagination semantics, error behavior, and rate limits beyond the quota note.

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?

Three short sentences, front-loaded with the purpose. Minimal waste, though the quota note repeats a point already made in the all_pages schema description.

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 annotation coverage and full schema coverage, the description is adequate but thin. It lacks return shape hints, pagination continuation guidance (mentioned only in schema for max_items), and does not help the agent choose between this and sibling form tools.

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 the schema carries the parameter documentation burden. The description's mention of 'bounded all_pages' adds minor context but is largely redundant with the schema's own description of all_pages.

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+resource ('List form submissions'), which is clear on its own. It doesn't explicitly distinguish itself from sibling list_forms or get_form, but the resource (submissions) is distinct enough that an agent can infer differentiation.

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 indication of when to use this vs. siblings like list_forms or get_form, no prerequisites, no exclusions. The only usage hint is the note about all_pages quota consumption, which is behavioral rather than routing guidance.

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