List Recycled Project Action Plan Template References

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

Annotations already indicate it's read-only and idempotent. The description adds that it returns a paginated JSON array with pagination metadata, which goes beyond annotations and helps the agent understand the response structure.

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 five sentences, each serving a purpose: stating the function, usage guidance, pagination, required parameters, and API reference. No unnecessary 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?

The description mentions returning a paginated JSON array of Action Plans (though the resource is template references, a minor inconsistency). It does not describe the output fields or structure, which is notable given there is no output schema. It provides sufficient information for basic use but lacks details on response content.

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 adds value by explaining how page and per_page control pagination, which supplements the schema descriptions with usage guidance.

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 it lists recycled project action plan template references, with a specific verb and resource. The title and description distinguish it from non-recycled counterparts by including 'Recycled' and referencing the recycle bin endpoint.

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 explains when to use the tool: for paginated overview, finding IDs, or filtering. It gives clear context on pagination and required parameters, but does not explicitly mention when not to use it or suggest alternatives among the many siblings.

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