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 mentions 'POST' (implying a write operation) but does not disclose critical behavioral traits: whether this is idempotent, destructive (e.g., overwrites existing data), requires specific permissions, has rate limits, or what the sync entails (e.g., merging, replacing). The description is minimal and fails to compensate for the lack of annotations.

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 brief and front-loaded with the core action ('Sync Budget Line Items'), followed by category and endpoint. It avoids unnecessary verbosity. However, it could be more structured (e.g., separating purpose from technical details) and slightly under-specified, but it earns points for not being wasteful.

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 of a sync operation (likely involving data mutation), no annotations, no output schema, and minimal description, this is inadequate. The description does not explain what 'sync' means, the expected outcome, error handling, or prerequisites. For a tool with two required parameters and potential side effects, it leaves too many gaps for effective agent use.

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 parameters 'project_id' and 'budget_line_items' documented in the schema. The description adds no additional meaning about these parameters—no context on what 'budget_line_items' array should contain or the sync logic. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, though no extra value is provided.

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 'Sync Budget Line Items. [Construction Financials/Budget] POST /rest/v1.0/budget_line_items/sync' restates the tool name ('Sync Budget Line Items') without adding specificity. It includes a category tag and API endpoint, but lacks a clear verb+resource explanation (e.g., what 'sync' means operationally) and does not distinguish it from sibling tools like 'create_budget_line_item' or 'update_budget_line_item'. This is borderline tautological.

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. With many sibling tools related to budget line items (e.g., create, update, list), there is no indication of when synchronization is appropriate—such as for batch updates, data integration, or conflict resolution. This absence of context leaves the agent without usage direction.

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