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' (a write operation) but doesn't disclose any behavioral traits: no information on permissions required, whether this overwrites existing rates, if it's idempotent, rate limits, or what happens on success/failure. The HTTP method (POST) is mentioned, but that's structural rather than behavioral 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 concise—two short phrases and an endpoint reference. It's front-loaded with the core action. However, the endpoint detail 'POST /rest/v1.0/companies/{company_id}/currency_configuration/exchange_rates' is redundant for an AI agent that doesn't need HTTP details, slightly reducing efficiency.

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 (create), the description is incomplete. It lacks critical context: what the tool returns, error conditions, side effects, or how it fits into the broader currency configuration system. The agent is left guessing about the outcome and usage constraints.

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 already documents parameters (company_id, base_currency_iso_code, exchange_rates). The description adds no additional meaning about these parameters—it doesn't explain what 'exchange_rates' should contain (e.g., target currencies and rates) or format expectations. Baseline 3 is appropriate since the schema does the heavy lifting.

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 Company Exchange Rates' states the action (create) and resource (company exchange rates), but it's vague about what exchange rates are being created. It doesn't specify whether this is for configuring currency conversions, setting rates for a period, or something else. The addition of '[Construction Financials/Currency Configurations]' provides some domain context but doesn't clarify the specific purpose.

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 doesn't mention prerequisites (e.g., needing a company ID), related tools for updating or viewing exchange rates, or scenarios where this is appropriate. The sibling tools list includes 'create_project_exchange_rates', but no distinction is made between company-level and project-level usage.

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