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 Submittal,' which implies a destructive operation, but doesn't disclose critical behavioral traits like whether deletion is permanent, reversible, requires specific permissions, or has side effects (e.g., cascading deletions). The API path hints at a REST DELETE but adds minimal context.

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 Submittal'). The API path adds technical detail but is not overly verbose. It could be slightly improved by integrating the context more seamlessly, but it's efficiently structured with zero waste.

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 delete operation with no annotations and no output schema, the description is incomplete. It lacks information on permissions, consequences, error handling, or what happens post-deletion. For a mutation tool with significant impact, this is a notable gap that could hinder safe usage.

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 descriptions for 'project_id' and 'id' in the input schema. The description adds no additional parameter semantics beyond the schema. According to the rules, with high schema coverage, the baseline is 3 even with no param info in the description.

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 verb ('Delete') and resource ('Submittal'), which clarifies the basic action. However, it does not distinguish this tool from other delete operations in the sibling list (e.g., delete_submittal_v1_1 is unique, but the description doesn't highlight any specific scope or version context beyond the API path). It's clear but lacks sibling differentiation.

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. It mentions the API path '[Project Management/Submittals] DELETE /rest/v1.1/projects/{project_id}/submittals/{id}', which implies context but doesn't explicitly state prerequisites, conditions, or when not to use it. No alternatives are mentioned.

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