Show Recycled Action Plan Template Approver

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

Annotations already indicate read-only, idempotent behavior. The description adds no new behavioral context (e.g., permissions, side effects, rate limits). Given the high annotation coverage, the description does not extend transparency beyond what structured data already provides.

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 and includes essential information (purpose, return type, required params, API location). It is slightly verbose due to the redundant endpoint line but remains efficient overall.

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 covers the return type (JSON object) but inaccurately refers to 'Action Plans' instead of 'template approver'. The optional 'page' and 'per_page' parameters are not explained, though they are defined in the schema. With no output schema, the description could be more precise, but it is generally sufficient for a simple read operation.

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?

Input schema has 100% description coverage for all 4 parameters. The description merely repeats that 'project_id' and 'id' are required, which is already in the schema, adding no additional meaning or constraints. Baseline score of 3 is appropriate.

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 that this tool fetches full details of a recycled action plan template approver by identifier, specifying the endpoint and required parameters. However, it inaccurately refers to 'Action Plans' instead of 'Action Plan Template Approver', which slightly muddles the purpose but is still sufficiently clear.

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 says 'Use this to fetch' but does not differentiate from sibling tools like 'list_recycled_action_plan_template_approvers'. No explicit when-to-use or when-not-to-use guidance is provided, making it minimally adequate.

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