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', implying a destructive mutation, but does not disclose critical behavioral traits such as required permissions, whether deletion is permanent or reversible, side effects, or error conditions. The description adds minimal value beyond the implied mutation.

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 tautological statement and a technical endpoint reference. However, it is not front-loaded with useful information; the first part repeats the name, and the second part is API-specific. It avoids verbosity but wastes space on unhelpful content.

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 deletion operation with no annotations and no output schema, the description is incomplete. It fails to explain what an 'Item Response Set' is, the consequences of deletion, or what the tool returns. For a destructive tool, this lack of context is a significant gap.

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 clear parameter descriptions ('Unique identifier for the company', 'Item Response Set ID'). The description adds no additional parameter semantics beyond the schema. According to the rules, with high schema coverage, the baseline is 3 even with no param info in 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 'Delete Item Response Set' is a tautology that restates the tool name without adding clarity. It mentions the domain '[Project Management/Inspections]' and the HTTP method 'DELETE', but lacks a specific verb-resource combination that distinguishes it from sibling tools like 'delete_a_response' or 'delete_checklist_item_response'. The purpose remains vague about what an 'Item Response Set' is and what deletion entails.

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 deletion tools (e.g., 'delete_a_response', 'delete_checklist_item_response'), there is no indication of context, prerequisites, or exclusions. The agent is left without any usage instructions.

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