Delete Checklist Item Response

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

Annotations already indicate destructiveHint=true. The description redundantly states 'cannot be undone' but adds confusion by claiming deletion of Inspections rather than item responses. It fails to clarify scope or side effects.

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 repetitive, stating 'cannot be undone' and 'permanently removes the specified Inspections' twice. It includes unnecessary details like the Procore API path, which doesn't aid an AI agent. A concise, correct sentence would suffice.

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?

Without an output schema and with confusing content, the description fails to explain what the tool actually does (delete a single response, not inspections) and omits details like idempotency or error handling. It is incomplete and misleading.

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 covers both parameters with descriptions. The description only repeats that they are required, adding no extra semantic value beyond what the schema provides.

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 states it removes a Checklist Item Response but repeatedly says it permanently deletes 'Inspections', which is a different resource. This confusion undermines clarity and misstates the tool's actual purpose.

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?

The only usage guidance is to delete Inspections, which is incorrect. It doesn't specify when to use this tool vs other delete tools like delete_checklist_inspection, and it provides no context about prerequisites or alternatives.

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