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 'Create company user' which implies a write operation, but does not disclose behavioral traits such as required permissions, side effects, or error handling. The endpoint reference adds minimal technical context but lacks operational guidance.

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 very concise with a single sentence, front-loading the core action. It wastes no words, though the endpoint reference could be considered extraneous for an AI agent. Overall, it is efficiently structured.

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 complexity (28 parameters, no annotations, no output schema), the description is inadequate. It does not explain the creation process, return values, or potential errors. For a mutation tool with many parameters, more context is needed to guide proper 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%, so the schema fully documents all 28 parameters. The description adds no additional parameter semantics beyond the schema, which is acceptable given the high coverage, resulting in a baseline score of 3.

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 ('Create') and resource ('company user'), making the purpose explicit. However, it does not differentiate from sibling tools like 'create_company_user_v1_0', 'create_company_user_v1_1', etc., which appear to be similar versions, so it lacks sibling distinction.

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 versions like v1_0, v1_1), nor does it mention prerequisites or exclusions. It only includes a technical endpoint reference ('POST /rest/v1.0/users'), which does not help with usage decisions.

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