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 'Create' (implying a write/mutation) but doesn't disclose behavioral traits like required permissions, whether it's idempotent, error handling, or what happens on success/failure. The URL path hints at REST POST but doesn't explain behavior.

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 a single sentence with the core action and URL path, which is efficient. However, the bracketed '[Core/Equipment]' and URL details could be considered slightly extraneous without explanation, but overall it's well-structured and front-loaded.

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 no annotations, no output schema, and a mutation tool with 4 required parameters, the description is incomplete. It lacks information on permissions, side effects, return values, error cases, or how it differs from sibling tools, leaving significant gaps for an AI agent.

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 in the schema. The description adds no parameter semantics beyond what the schema provides, but the schema adequately documents all 4 required parameters, meeting the baseline for high coverage.

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 ('Create equipment make') and resource ('Project'), but it's vague about what an 'equipment make' is and doesn't distinguish from siblings like 'create_equipment_make_company_v2_0'. The URL path adds context but doesn't clarify purpose beyond the name.

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?

No guidance on when to use this tool versus alternatives like 'create_equipment_make_company_v2_0' or 'create_an_equipment_make'. The description includes '[Core/Equipment]' and a URL path, but these don't provide actionable usage context 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.