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 implies a read-only operation ('Show'), but does not explicitly state whether it's safe, if it requires specific permissions, or if it has rate limits. The inclusion of pagination parameters ('page', 'per_page') suggests it may return paginated results, but this is not explained.

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: one stating the purpose and the other providing the API endpoint. It is front-loaded with the core function, though the second sentence is more technical than explanatory for an AI agent.

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 and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., read-only nature, pagination behavior) and what the tool returns. For a tool with four parameters and no structured output information, more context is needed to guide the agent effectively.

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 descriptions for all parameters (e.g., 'UUID of the early pay program'). The description adds no additional parameter semantics beyond the schema, but the schema is comprehensive, so a baseline score of 3 is appropriate as it doesn't compensate for gaps but doesn't need to.

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 tool's purpose as 'Show Early Pay Program' and includes the API endpoint path, which clarifies it retrieves information about a specific early pay program. However, it does not differentiate from sibling tools like 'list_early_pay_programs' or 'update_early_pay_program', leaving ambiguity about when to use this specific 'show' tool versus others.

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. It does not mention prerequisites, such as needing a specific early_pay_program_id, or compare it to sibling tools like 'list_early_pay_programs' for broader queries or 'update_early_pay_program' for modifications.

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