Procore MCP Server

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

No annotations are provided, so the description carries full burden. It states 'DELETE' which implies a destructive operation, but doesn't disclose any behavioral traits: no information about permissions required, whether deletion is permanent or reversible, what happens to associated data, or error conditions. For a destructive operation with zero annotation coverage, this is a significant gap.

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 concise (one sentence plus API path) but poorly structured. It front-loads the purpose but wastes characters on '[Project Management/Inspections]' which adds little value. The API path 'DELETE /rest/v1.0/projects/{project_id}/checklist/items/{item_id}/item_response' could be useful for debugging but doesn't help the agent understand when to use the tool.

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 operation with no annotations and no output schema, the description is inadequate. It doesn't explain what a 'checklist item response' is, what gets deleted, whether there are side effects, or what the response looks like. The agent lacks critical context to use this tool safely and effectively in a project management/inspections domain.

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 description coverage is 100% with clear parameter descriptions ('Checklist Item ID' and 'Unique identifier for the project'). The description adds no parameter semantics beyond what the schema provides - it doesn't explain relationships between item_id and project_id, or provide context about valid values. With complete schema coverage, baseline 3 is appropriate.

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 'Delete Checklist Item Response' which clearly indicates the verb (delete) and resource (checklist item response). However, it doesn't differentiate from sibling tools like 'delete_checklist' or 'delete_checklist_item_attachment' - it's unclear what makes a 'checklist item response' distinct from other checklist-related entities. The description is functional but lacks specificity about the resource being deleted.

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 provides no guidance on when to use this tool versus alternatives. With many sibling deletion tools (delete_checklist, delete_checklist_inspection, delete_checklist_section, etc.), there's no indication of what a 'checklist item response' is or when one would need to delete it specifically. The agent must infer usage from the name alone.

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