Delete Checklist (Inspection)

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

The description adds rich behavioral detail beyond the annotations: 'Permanently removes the checklist', 'This cannot be undone', 'a repeat call returns 404', and a breakdown of common HTTP error statuses (401, 403, 404). The project_id defaulting note introduces an inconsistency with the required-parameter list, slightly detracting from full transparency.

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 generally well-structured and front-loaded, covering preconditions, consequences, error handling, and endpoint in a dense but readable way. The contradictory sentence about project_id defaulting is a flaw that prevents it from being fully concise and accurate.

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?

It covers essentially all relevant context: id resolution, irreversibility, repeat-call behavior, error statuses, API version, and endpoint. The project_id defaulting/required inconsistency creates a completeness gap, as it leaves unclear whether the tool can operate without an explicit project_id.

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?

Although the schema already covers both parameters (100% coverage), the description adds a misleading claim that project_id defaults when omitted, even though it is marked required in both the schema and the description itself. This contradiction could cause an agent to incorrectly omit project_id, making the description worse than the schema alone.

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 'Deletes specified Checklist (Inspection)' with a specific verb and resource, and includes the exact endpoint (DELETE /rest/v1.1/projects/{project_id}/checklist/lists/{id}), clearly distinguishing it from sibling delete tools like delete_checklist and delete_checklist_schedule.

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?

It instructs to confirm the target id with the matching show or list tool before calling and to resolve the id with a list tool first. However, the statement 'project_id defaults to the value set by procore_set_config when omitted' conflicts with the later 'Required parameters: id, project_id' and the schema, creating ambiguity about when project_id may actually be omitted.

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