Delete Checklist Item Response

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

Beyond the annotations, the description discloses irreversibility ('Permanently removes... This cannot be undone'), repeat call behavior ('a repeat call returns 404'), and likely error statuses ('401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve'). This is rich behavioral context that annotations alone do not provide.

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 dense but well-structured, front-loading the core purpose and then adding usage prerequisites, behavioral consequences, error patterns, and API reference. Every sentence carries useful information, though it could be slightly trimmed without losing meaning.

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?

For a destructive tool with two parameters and no output schema, the description is exceptionally complete. It covers what is deleted, how to prepare (resolve IDs), default behavior of project_id, irreversibility, repeat call outcome, common error statuses, required parameters, and the exact API endpoint. This leaves little ambiguity for an agent.

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?

The schema already describes both parameters as URL path parameters with 100% coverage, so the baseline is 3. The description adds semantics for item_id ('must identify an existing parent record') but creates a contradiction by stating 'project_id defaults to the value set by procore_set_config when omitted' while the schema and the description itself list project_id as required. This inconsistency undermines the added value.

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 opens with a specific verb and resource: 'Removes the Checklist Item Response for a specified Checklist Item.' It clearly identifies the operation as a deletion of a checklist item response, which is distinct from sibling tools. It also includes the endpoint for additional 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?

The description gives explicit preconditions: 'Confirm the target id with the matching show or list tool before calling' and 'resolve it with the matching list tool first.' It also notes the project_id default from procore_set_config. It does not explicitly state when not to use the tool, but the guidance on resolving IDs is strong.

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