Procore MCP Server

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

No annotations are provided, so the description carries the full burden. It states 'Delete', implying a destructive operation, but does not disclose behavioral traits such as whether deletion is permanent or reversible, what permissions are required, or what happens to associated data. The HTTP method 'DELETE' is mentioned, but this adds little beyond the tool name. For a destructive tool 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 and front-loaded with the core action. It includes additional context (category and API endpoint) which, while not strictly necessary, is not wasteful. The structure is clear, though it could be more streamlined by omitting the API path.

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 tool's destructive nature, no annotations, and no output schema, the description is incomplete. It fails to address critical aspects like the permanence of deletion, error conditions, or return values. For a deletion tool in a complex system with many siblings, this leaves the agent under-informed about risks and outcomes.

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 input schema has 100% description coverage, with clear parameter definitions ('Checklist ID' and 'Unique identifier for the project.'). The description adds no parameter semantics beyond the schema, not explaining relationships or constraints. With high schema coverage, the baseline is 3, as the schema does the heavy lifting.

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 'Delete Checklist (Inspection)' states the action (delete) and resource (checklist inspection), but it's vague about what a 'checklist inspection' entails. It distinguishes from siblings by specifying 'Inspection' in parentheses, but many sibling tools also involve checklists, so differentiation is minimal. The description is functional but lacks specificity.

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 tools like 'delete_checklist', 'delete_checklist_inspection_v1_1', and 'restore_deleted_checklist_inspection', there is no indication of context, prerequisites, or exclusions. This leaves the agent guessing about appropriate usage.

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