Procore MCP Server

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

No annotations are provided, so the description carries full burden. It states 'Update' which implies a mutation/write operation, but doesn't disclose any behavioral traits: no information about permissions required, whether changes are reversible, side effects, rate limits, or what happens to unspecified fields. The API path suggests PATCH semantics but this isn't explained. For a mutation tool with 15 parameters and no annotation coverage, this is a significant gap.

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 technically concise (one sentence plus API path) but inefficiently structured. The first part 'Update Direct Cost Line Item' is redundant with the name, while the API path provides technical implementation details that don't help an AI agent understand when or how to use the tool. The information is front-loaded but not helpful - every sentence should earn its place, and the API path doesn't add meaningful guidance for tool selection.

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 (15 parameters, mutation operation, no annotations, no output schema), the description is severely incomplete. It doesn't address the tool's behavior, error conditions, required permissions, or typical use cases. For a financial data mutation tool with many parameters, the description should provide much more context about what constitutes a valid update, field dependencies, and business logic 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 all 15 parameters with descriptions. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters, provide examples, or clarify usage patterns. The baseline of 3 is appropriate when the schema does the heavy lifting, though the description could have added value by explaining which fields are commonly updated together.

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 'Update Direct Cost Line Item' is a tautology that restates the tool name without adding meaningful context. It includes an API endpoint path '[Construction Financials/Direct Costs] PATCH /rest/v1.0/projects/{project_id}/direct_costs/{direct_cost_id}/line_items/{id}', which provides technical routing but doesn't clarify what the tool actually does beyond the obvious 'update' action. No specific verb+resource distinction or sibling differentiation is provided.

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 zero guidance on when to use this tool versus alternatives. With 15 sibling tools including other update operations (like update_direct_cost_item, update_budget_line_item, etc.), there's no indication of context, prerequisites, or differentiation. The API path hints at a hierarchical structure but offers no practical usage instructions.

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