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 mutation, but does not disclose behavioral traits such as permissions required, whether deletion is permanent or reversible, or any side effects (e.g., impact on associated checklists). This is a significant gap for a destructive operation.

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 an API endpoint path for context, which is efficient. However, the bracketed category '[Project Management/Inspections]' adds minor clutter without clear utility.

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, lack of annotations, and no output schema, the description is incomplete. It fails to address critical context like success/error responses, confirmation requirements, or dependencies. For a deletion tool, this leaves the agent with insufficient information to use it safely.

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 Template ID' and 'Unique identifier for the project.'). The description adds no additional parameter semantics beyond the schema, but the schema is sufficient. Baseline 3 is appropriate 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 states the action ('Delete') and resource ('Project Checklist Template'), which is clear but basic. It does not differentiate from sibling tools like 'delete_project_checklist_template_v1_1' or other deletion tools, leaving ambiguity about when to use this specific version. The purpose is understandable 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 deletion tools (e.g., 'delete_project_checklist_template_v1_1'), there is no indication of differences, prerequisites, or exclusions. This absence makes it difficult for an agent to select the correct tool.

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