List Forms On A Project

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

Annotations already declare readOnlyHint=true, idempotentHint=true. The description adds that it returns a 'paginated JSON array of Forms' and mentions pagination parameters, required project_id, and the API endpoint. This goes beyond annotations with specific return format and endpoint info.

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 concise with multiple sentences but no wasted words. It front-loads the core purpose, then adds usage, return type, pagination, required param, and API reference. It could be slightly more compact but is well-structured.

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 has 11 parameters, 1 required, no output schema, and safe annotations, the description covers purpose, usage, pagination, required param, and API source. It lacks information about what constitutes a 'Form' or authentication/rate limits, but is sufficiently complete for a read-only list tool.

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 coverage is 100%, so baseline is 3. The description mentions that project_id is a required URL path parameter and that page/per_page control pagination, but adds limited detail beyond what the schema already provides. It does not explain filter parameters in depth.

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 'Return a list of all Forms' and the resource 'a specified Project'. It specifies enumeration, pagination, filtering, and finding IDs, distinguishing it from other list tools (e.g., list_forms vs list_checklists).

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 explicit usage scenarios: 'Use this to enumerate Forms when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not state when not to use it or alternatives, but the context is clear.

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