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 'Delete' which implies a destructive mutation, but doesn't disclose critical behavioral traits like whether this is permanent, requires specific permissions, has side effects on related data, or returns confirmation. The HTTP method 'DELETE' is mentioned, but this is technical rather than semantic 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 brief and front-loaded with the core action. However, it includes technical details like the API endpoint path that don't add semantic value for an AI agent. The sentence could be more focused on the operational context rather than implementation details.

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?

For a destructive operation with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after deletion, whether it's reversible, what permissions are needed, or what the response contains. Given the complexity of budget line items in construction financials, more context is needed.

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 all three parameters clearly documented in the schema. The description adds no additional parameter semantics beyond what's in the schema. The baseline is 3 since the schema does the heavy lifting, but the description doesn't compensate with any contextual parameter information.

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 clearly states the action ('Delete') and the resource ('Budget Line Item'), and provides context with '[Construction Financials/Budget]'. It distinguishes from siblings by specifying the exact resource type, though it doesn't explicitly differentiate from other delete operations like 'delete_a_budget_change' or 'delete_budget_modification'.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, consequences, or when this operation is appropriate compared to other budget-related delete tools in the sibling list.

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