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 mutation, but gives no behavioral details: no warning about irreversibility, no mention of permissions required, no rate limits, no error conditions, and no indication of what the response looks like. The API endpoint path adds technical context but doesn't compensate for the missing behavioral disclosure.

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 extremely concise - just two brief statements. The first sentence states the action, the second provides the API endpoint. There's no wasted verbiage. However, the conciseness comes at the cost of completeness, as critical information is omitted for a destructive operation.

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 deletion tool with no annotations and no output schema, the description is severely incomplete. It doesn't explain what a specification area is, what gets deleted, whether deletion is reversible, what permissions are needed, or what the response contains. The API endpoint provides technical routing but doesn't address the operational context an AI agent needs to safely invoke this tool.

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 all three parameters clearly documented as unique identifiers for company, project, and specification area. The description adds no parameter semantics beyond what the schema already provides. Since schema coverage is high, the baseline score of 3 is appropriate, though the description doesn't add any value regarding parameter usage or relationships.

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 Specification Area' is a tautology that merely restates the tool name. It adds the API endpoint path '[Project Management/Specifications] DELETE /rest/v2.1/companies/{company_id}/projects/{project_id}/specification_areas/{specification_area_id}', which provides technical context but doesn't explain what a 'Specification Area' is or what deletion entails. Compared to sibling tools like 'create_specification_area_v2_1', it doesn't differentiate beyond the obvious verb difference.

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 zero guidance on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing proper permissions), consequences of deletion, or what happens to associated data. Given the destructive nature implied by 'Delete', this lack of usage context is particularly problematic for an AI agent.

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