List Recycled Company Form Templates

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

Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds context by mentioning pagination, metadata, required parameter company_id, and the exact API endpoint, all consistent with annotations. No contradictions.

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 4 sentences, front-loading purpose and usage. Each sentence adds value, though it could be slightly more concise. It is well-structured with no wasted words.

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 (listing recycled form templates), the description covers purpose, usage, pagination, required parameters, and the API endpoint. No output schema exists, but the description states it returns a paginated JSON array with metadata, which is sufficient.

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 page and per_page for pagination and company_id as required, but does not add significant meaning beyond the schema descriptions already present.

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 tool returns a collection of Recycled Form Templates for a specified Company, with verbs like 'Returns' and 'enumerate'. It specifies the resource (recycled form templates) and scope (company), and distinguishes from siblings like delete_company_form_template and restore_company_form_template.

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 clear use cases: 'Use this to enumerate Forms when you need a paginated overview, to find IDs, or to filter by query parameters.' It gives context but does not explicitly state when not to use or mention alternatives, though it's implicit.

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