Delete Company Inspection Template Item

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds valuable context beyond this: 'Permanently removes... This cannot be undone, and a repeat call returns 404' and explains error payload behavior. This meaningfully extends the annotation-only safety profile, though it doesn't describe a successful response body.

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 a single dense paragraph of about five sentences. Each sentence contributes essential information (purpose, prerequisites, permanence, error handling, required parameters, endpoint). It could be slightly more streamlined, but it remains efficient and well-organized.

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 destructive nature, three required parameters, and no output schema, the description covers prerequisites, permanent effects, repeat-call behavior, and common HTTP error statuses. It omits what a successful response looks like, but for a delete operation this is a minor gap. Overall it is highly complete.

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 each parameter described as a URL path parameter. The description adds useful context about resolving parent records and the default for company_id, but it also introduces a conflict: it says company_id defaults when omitted while the schema marks it as required. The added semantics are helpful but not necessary given the schema's complete coverage.

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 uses a specific verb 'Deletes' and names the exact resource: 'Company Inspection Template Item for a specified Company.' This distinguishes it from sibling tools like update_company_inspection_template_item and delete_company_inspection_template_item_reference by its action and resource scope.

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?

Provides explicit usage guidance: 'Confirm the target id with the matching show or list tool before calling' and 'resolve them with the matching list tool first.' It also details likely error statuses (401, 403, 404), giving the agent clear context for when and how to use this tool safely.

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