Show Recycled Company Action Plan Template

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds the endpoint method (GET) and API version, but no additional behavioral traits beyond what annotations provide. Does not disclose potential errors, permissions, or rate limits.

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?

Description is concise at three sentences, front-loaded with purpose. Could be slightly streamlined (e.g., removing 'Returns... Returns...' redundancy), but overall well-structured and efficient.

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?

For a read-only tool with complete annotations and schema, the description adds the endpoint path and API version. However, it does not clarify the purpose of page/per_page parameters (which seem unnecessary for a single-item fetch) or what the returned JSON object contains. Lacks details on response structure or error handling.

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 baseline is 3. The description only restates the required parameters (company_id, id) already marked as required in schema. No additional meaning or context about parameter usage beyond what the schema defines.

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?

Clearly states it returns a specific Recycled Company Action Plan Template, with verb 'Returns' and resource identified. The title and description mention 'Recycled' and 'Company Action Plan Template', which helps distinguish from sibling tools like show_company_action_plan_template (active) and show_recycled_action_plan (different entity). However, it does not explicitly contrast with siblings.

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?

Says 'Use this to fetch the full details of a specific Action Plans by its identifier,' which implies usage context but provides no guidance on when not to use or alternatives. Does not exclude scenarios or compare with related tools like show_company_action_plan_template.

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