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 operation, but does not disclose critical behavioral traits such as required permissions, whether the deletion is permanent or reversible, error handling, or confirmation prompts. The REST endpoint hint adds minimal context.

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 and front-loaded with the core action. It consists of a single sentence followed by a REST endpoint, which is efficient. However, the endpoint detail may be extraneous for an AI agent's decision-making, slightly reducing conciseness.

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 destructive nature, lack of annotations, and no output schema, the description is incomplete. It fails to address key contextual aspects like side effects, success/error responses, or safety warnings, which are crucial for a deletion tool in a complex system with many sibling operations.

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 in the input schema. The description adds no additional parameter semantics beyond the schema, but since the schema is well-documented, the baseline score of 3 is appropriate as the description does not compensate but also does not detract.

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 tool's purpose as 'Delete Managed Equipment Maintenance Log Attachment', which is a specific verb+resource combination. However, it does not distinguish from sibling tools like 'bulk_delete_managed_equipment_maintenance_log_attachments' or 'delete_managed_equipment_attachment', leaving ambiguity about when to use this single-delete tool versus bulk operations.

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 includes a category tag '[Project Management/Field Productivity]' and a REST endpoint, but these do not offer practical usage instructions, prerequisites, or comparisons with sibling delete tools.

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