Procore MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Show First Prime Contract' and includes an API endpoint, but does not clarify if this is a read-only operation, what data is returned, any side effects, authentication needs, rate limits, or error conditions. The term 'show' is ambiguous—it could imply a safe read, but without explicit confirmation, the agent cannot reliably assess risks. The description adds minimal behavioral context beyond the name.

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 parts: a restated name and an API endpoint. It is front-loaded but under-specified, as it lacks essential details. However, it avoids redundancy and is structured efficiently, with no wasted words. The brevity is appropriate, though it sacrifices clarity for conciseness.

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 (a tool with pagination parameters for retrieving a 'first' contract), no annotations, and no output schema, the description is incomplete. It does not explain what 'first' means, the return format, or how pagination interacts with the 'first' concept. The agent must infer behavior from the schema alone, which is insufficient for reliable use. The description fails to compensate for the lack of structured metadata.

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?

The input schema has 100% description coverage, with clear parameter definitions (project_id, page, per_page). The description does not add any semantic details about parameters beyond what the schema provides (e.g., explaining why pagination is needed for a 'first' contract or how project_id relates to the result). Since schema coverage is high, the baseline score is 3, reflecting adequate but no extra value from the description.

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 'Show First Prime Contract. [Construction Financials/Prime Contracts] GET /rest/v1.0/prime_contract' restates the tool name ('Show First Prime Contract') with minimal added context. It includes a category hint ('Construction Financials/Prime Contracts') and API endpoint, but does not clearly specify what 'show' means (e.g., retrieve details, list, or display) or what 'first' implies (e.g., earliest, primary, or a specific ordering). This is vague and borders on tautology, failing to distinguish it from potential siblings like 'list_prime_contracts' or 'show_prime_contract'.

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 any prerequisites, context for 'first' (e.g., based on date, status, or project hierarchy), or refer to sibling tools. Given the many sibling tools (e.g., 'list_prime_contracts', 'show_prime_contract'), this lack of differentiation leaves the agent without direction on appropriate usage scenarios.

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