Show Recycled Checklist Template

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

Annotations provide readOnlyHint, destructiveHint, idempotentHint. Description adds that it returns a JSON object and specifies the endpoint (GET), consistent with read-only behavior. However, it mistakenly refers to 'Inspections' instead of 'Checklist Templates', introducing a minor inconsistency. No additional behavioral details beyond what annotations imply.

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 4 sentences and relatively concise, but it repeats the title verbatim and includes API details that may not be essential for an AI agent. Information is front-loaded, but there is some redundancy.

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 presence of annotations and full parameter schema, the description adequately conveys the purpose and return type. However, it does not explain that this is for recycled templates (context of recyle bin), nor does it mention optional pagination parameters (page, per_page) that could affect usage. Minor gaps in completeness.

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% with clear descriptions for each parameter. Description only repeats that project_id and id are required, adding no new meaning. The baseline is 3 since the schema already fully documents parameters.

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 fetches full details of a recycled checklist template by identifier. However, it inconsistently uses 'Inspections' instead of 'Checklist Templates', which could confuse an AI agent about the exact resource. The tool name and endpoint make the purpose clear, distinguishing it from siblings like show_checklist_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?

No guidance on when to use this tool versus alternatives. It does not specify that it is for recycled (deleted) templates or when to prefer it over show_checklist_template. Required parameters are listed, but without context of when to invoke this tool.

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