Delete Project Inspection Template Item Reference

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

The description reinforces the destructive nature already indicated by annotations (destructiveHint: true), stating 'cannot be undone' and 'permanently removes.' This adds clarity but does not disclose additional behaviors like cascading effects or authorization needs. No contradiction with annotations.

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 includes 5 sentences but repeats 'cannot be undone' and 'permanently removes' twice. Includes API endpoint which is useful but could be more concise. Slightly redundant but structured.

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?

As a destructive tool with no output schema, the description fails to explain expected return values or prerequisites (e.g., item reference must exist). Missing details on success response or error conditions, leaving 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?

Input schema has 100% coverage with descriptions for all three required parameters. The description only lists the same parameter names without adding meaning beyond the schema. No additional semantic guidance provided.

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 title and first sentence clearly state the tool deletes a project inspection template item reference. However, the description says 'permanently delete the specified Inspections' which may confuse agents into thinking it deletes inspections rather than item references, causing ambiguity.

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 like 'delete_company_inspection_template_item_reference' or other delete tools. Lacks context for selecting this tool over siblings. No when-not-to-use or conditional advice provided.

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