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 of behavioral disclosure. It states 'Delete Checklist' but does not clarify if this is permanent, reversible, requires specific permissions, or has side effects (e.g., cascading deletions). The HTTP method 'DELETE' hints at a destructive operation, but explicit warnings or behavioral details are missing, making it insufficient for a mutation tool.

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 ('Delete Checklist'). The additional context ('[Project Management/Inspections] DELETE /rest/v1.0/checklist/lists/{id}') is somewhat redundant but provides API route information efficiently. No unnecessary sentences are present.

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 is a destructive operation with no annotations and no output schema, the description is incomplete. It lacks critical information about permissions, irreversibility, error conditions, or response format. For a delete tool, this gap is significant, as the agent cannot assess risks or interpret outcomes adequately.

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 both parameters ('id' and 'project_id') clearly documented in the schema. The description adds no additional semantic context (e.g., explaining relationships between checklist ID and project ID). Since the schema does the heavy lifting, the baseline score of 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 clearly states the action ('Delete') and resource ('Checklist'), making the purpose explicit. It does not explicitly differentiate from sibling tools (e.g., other delete operations like 'delete_checklist_inspection'), but the verb+resource combination is specific enough for basic understanding.

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 (e.g., other deletion tools in the sibling list like 'delete_checklist_inspection' or 'delete_checklist_section'). There is no mention of prerequisites, consequences, or contextual constraints, leaving the agent without usage direction.

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