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 doesn't disclose behavioral traits like whether deletion is permanent, requires specific permissions, has side effects (e.g., stopping event deliveries), or returns confirmation. The API endpoint hint suggests a REST DELETE operation, but this isn't explicitly explained.

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 a single sentence with the tool name, platform tag, and API endpoint. It's concise but under-specified—the platform tag and endpoint are extraneous for an agent's understanding. The structure is front-loaded with the action but lacks needed elaboration.

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 and no output schema, the description is incomplete for a destructive operation. It doesn't cover behavioral context, success/error responses, or usage scenarios. The API endpoint detail doesn't compensate for missing operational guidance.

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' and 'Webhooks Hook ID'). The description adds no additional parameter semantics beyond the schema, but the schema is fully self-documented, meeting the baseline for high coverage.

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 Company Webhooks Hook' restates the tool name and adds a platform tag and API endpoint, but it's a tautology that doesn't clarify what a 'webhooks hook' is or what deletion entails. It distinguishes from siblings by specifying 'Company' scope, but the purpose remains vague beyond the literal name.

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 (e.g., project-level webhook deletion, bulk deletion tools, or when deletion is appropriate). The description lacks any context about prerequisites, consequences, or typical use cases.

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