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 of behavioral disclosure. It states 'Create' which implies a write operation, but does not disclose any behavioral traits such as required permissions, whether it's idempotent, rate limits, or what happens on success/failure. This leaves the agent with insufficient information to understand the tool's 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 concise with a single sentence, but it is under-specified rather than efficiently informative. It includes an API endpoint path which may be redundant for the agent's understanding. While not verbose, it fails to front-load useful information, making it minimally adequate but not helpful.

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's complexity (7 parameters, including nested objects) and the absence of annotations and output schema, the description is incomplete. It does not explain what an 'Early Pay Program' is, its purpose, or the implications of creation. For a mutation tool with no structured behavioral data, this description leaves significant gaps for the 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%, meaning all parameters are documented in the schema. The description adds no additional parameter semantics beyond the schema. According to the rules, with high schema coverage, the baseline is 3, which is appropriate here as the description does not compensate but also does not detract.

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 'Create Early Pay Program' is a tautology that restates the tool name without adding specificity. It lacks a clear verb-resource-action statement and does not distinguish this tool from sibling tools like 'update_early_pay_program' or 'deactivate_early_pay_program', leaving the agent uncertain about its unique function.

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 sibling tools like 'update_early_pay_program' and 'deactivate_early_pay_program', but the description fails to mention any prerequisites, context, or distinctions, offering no help for the agent in selecting the correct tool.

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