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 'Bulk Delete Triggers' which implies a destructive mutation, but doesn't disclose critical behaviors: whether deletion is permanent/reversible, what permissions are required, if there are rate limits, or what happens on success/failure. The endpoint hint suggests a REST API call but lacks operational context needed for safe agent use.

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 extraneous details like the platform tag and endpoint which might be redundant if the agent has other metadata. The two additional fragments don't add clarity to the core purpose, but overall it's not verbose.

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 no annotations, no output schema, and a destructive operation, the description is incomplete. It lacks essential context: what triggers are, the impact of bulk deletion (e.g., all triggers for a hook), error handling, and response format. The platform/endpoint hints don't substitute for behavioral disclosure needed for a mutation 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 one parameter 'hook_id' documented as 'Webhooks Hook ID'. The description adds no parameter semantics beyond this—it doesn't explain what a hook ID is, where to find it, or if triggers are scoped to this hook. Since schema coverage is high, baseline 3 is appropriate, but the description doesn't compensate with any additional parameter insights.

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 'Bulk Delete Triggers' which indicates the action (delete) and resource (triggers), but it's vague about scope and context. It doesn't specify what triggers are (e.g., webhook triggers) or distinguish from sibling tools like 'bulk_delete_project_webhooks_triggers_v2_0' or 'bulk_delete_company_webhooks_triggers_v2_0'. The platform context is mentioned but not integrated into the purpose statement.

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 on when to use this tool versus alternatives. The description includes a platform tag '[Platform - Developer Tools/Webhooks]' and an endpoint 'DELETE /rest/v1.0/webhooks/hooks/{hook_id}/triggers/bulk', but doesn't explain when this bulk deletion is appropriate versus individual trigger deletion or other bulk operations. No prerequisites, exclusions, or sibling tool comparisons are provided.

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