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 an equipment make' which implies a destructive operation, but doesn't disclose whether this requires specific permissions, if deletion is permanent/reversible, what happens to associated data, or any rate limits/constraints. The description is minimal and lacks behavioral 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 with two sentences, but the second sentence contains technical endpoint details ('DELETE /rest/v1.0/companies/{company_id}/managed_equipment_makes/{id}') that may not add value for an AI agent. The first sentence is clear, but overall structure could be more focused on agent guidance.

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 operation with no annotations and no output schema, the description is inadequate. It doesn't explain what an 'equipment make' is, the implications of deletion, error conditions, or return values. Given the complexity and lack of structured data, more context is needed.

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 (company_id, id) clearly documented in the schema. The description adds no additional parameter semantics beyond the schema, so the baseline score of 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 clearly states the action ('Delete') and resource ('an equipment make'), providing a specific verb+resource combination. It doesn't explicitly differentiate from sibling tools like 'delete_equipment_make_company_v2_0' or 'delete_an_equipment_model', but the purpose is unambiguous.

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. There are multiple delete-related sibling tools (e.g., delete_equipment_make_company_v2_0, delete_an_equipment_model), but no indication of which to choose or any prerequisites for deletion.

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