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 indicates a destructive 'DELETE' operation and 'bulk_destroy' in the path, implying permanent deletion. However, it lacks details on permissions required, whether deletions are reversible, rate limits, or confirmation prompts. The description adds minimal behavioral context beyond the implied destructiveness.

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 brief statement of purpose and the HTTP method/path. It is front-loaded with the main action. However, the bracketed '[Project Management/Coordination Issues]' is vague and could be omitted or clarified to improve structure. Overall, it is efficient with minimal waste.

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 tool's complexity (bulk destructive operation with 3 required parameters), no annotations, and no output schema, the description is inadequate. It fails to explain critical aspects like error handling, response format, or side effects. The lack of behavioral transparency and usage guidelines leaves significant gaps for an AI agent to safely invoke this tool.

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 (e.g., 'Unique identifier for the project'). The description adds no parameter-specific information beyond what the schema provides. However, it implicitly references 'item_type' via the enum 'rfi' in the path, but this is already covered in the schema. The baseline score of 3 is appropriate as 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 states the action ('Bulk Delete') and resource ('Procore Item Associations'), which is clear. However, it does not distinguish this tool from other bulk delete tools (e.g., 'bulk_delete_materials', 'bulk_delete_time_and_material_timecards') or specify what 'Procore Item Associations' are, leaving the purpose somewhat vague. It avoids tautology by adding the HTTP method and path, but lacks specificity about the resource's nature.

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 mentions '[Project Management/Coordination Issues]' in brackets, which might hint at a context but is ambiguous and not explicit. There is no mention of prerequisites, when-not-to-use scenarios, or sibling tool comparisons (e.g., 'delete_procore_item_association' for single deletions).

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