List Forms

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

Annotations already declare readOnly, idempotent, destructive=false, and openWorld. The description adds genuinely new behavioral context beyond those: pagination is bounded, every page consumes API quota, and all_pages is not a snapshot or guaranteed complete backup. That quota warning and the 'not a backup' caveat are meaningful additions.

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, no filler, with the resource and the two key behavioral caveats (bounded pages, quota cost) front-loaded. Nothing repeats the structured fields.

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?

With no output schema, the description is still adequate: annotations carry the safety profile and the schema carries parameter details, while the description contributes the quota/pagination caveats. It leaves vague what 'community data' encompasses and gives no default-page behavior, so not fully complete.

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 all six parameters are already documented, including all_pages and max_items semantics. The description only echoes the quota angle for all_pages rather than adding syntax, defaults, or interaction details beyond the schema, so the baseline of 3 applies.

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 and resource ('List Forms') and adds a scope note ('Reads community data'). It doesn't differentiate itself from siblings like get_form or get_form_submissions, but the name and phrasing make the operation unambiguous.

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 guidance on when to use this versus get_form, get_form_submissions, or search-style siblings, and no prerequisites or exclusions. The only usage-adjacent sentence is about all_pages quota behavior, not about selecting this tool.

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