Delete Company Inspection Template Item Reference

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

Description contradicts annotations: title annotation says 'Delete Company Inspection Template Item Reference' but description says delete 'Inspections'. This is a clear contradiction, scoring 1. Additionally, no disclosure of cascading effects or error conditions.

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 verbose and repetitive, stating 'cannot be undone' and 'permanently removes' twice each. Could be condensed to a single clear sentence.

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?

No output schema; description does not clarify return value (e.g., success response) or potential error scenarios. Lacks completeness for a delete 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?

Schema coverage is 100% with clear descriptions for all three parameters. Description only lists required params without adding new meaning, meeting baseline.

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?

Description states 'delete the specified Inspections' but tool name and schema refer to 'Company Inspection Template Item Reference'. This mismatch confuses the resource being deleted, undermining purpose clarity.

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 vs. alternatives like show, update, or list. No distinction between company-level and project-level references, and no exclusions provided.

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