Restore A Recycled Company Checklist Template

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

Annotations provide readOnlyHint=false and destructiveHint=false, but the description adds confusion by describing an update operation rather than clarifying the restore behavior. It does not explain what 'restore' entails (e.g., bringing back from recycle bin) or what happens to the resource.

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 verbose and includes contradictory information. It could be shortened to 'Restores a recycled company checklist template' without the confusing update details. Not concise.

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 lack of output schema and the tool's specific purpose (restore from recycle bin), the description fails to explain the effect of the operation, success/failure conditions, or the format of the return value. It is incomplete.

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 descriptions already present. The description only re-states required parameters without adding new meaning or usage context. 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 mixes restoration and update concepts: 'Restores' suggests bringing back a deleted template, but then says 'Use this to update an existing Inspections'. This contradiction makes the tool's primary action unclear, and it conflates two different resources (checklist template vs inspections).

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 sibling tools like 'restore_recycled_checklist_template' or 'restore_deleted_checklist_inspection'. There is no differentiation of use cases or exclusion criteria.

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