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 implies a write operation ('Create') but does not disclose behavioral traits such as permissions required, rate limits, idempotency, or what happens on failure. The HTTP method (POST) and endpoint hint at a mutation, but no safety or operational details are given, which is inadequate for a tool with potential side effects.

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 restated name and an endpoint. However, it lacks structure and front-loading of key information; the endpoint detail may be less helpful than explaining the tool's purpose. It avoids verbosity but under-specifies, making it less effective.

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 single parameter, the description is incomplete. It fails to explain what triggers are, what 'bulk' entails (e.g., batch size, input format), or the expected outcome. For a mutation tool in a webhooks context, this leaves significant gaps for an agent to understand and use it correctly.

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?

The input schema has 100% description coverage, with one parameter 'hook_id' documented as 'Webhooks Hook ID'. The description adds no additional parameter semantics beyond the schema, but since schema coverage is high, the baseline score of 3 is appropriate. No extra context about the parameter's role in bulk creation is provided.

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 'Bulk Create Triggers. [Platform - Developer Tools/Webhooks] POST /rest/v1.0/webhooks/hooks/{hook_id}/triggers/bulk' restates the tool name ('Bulk Create Triggers') without adding meaningful specificity. It includes a platform context and HTTP endpoint, but does not clearly explain what triggers are or what 'bulk create' entails in this context, making it vague. It distinguishes from siblings only by name, not by functional differentiation.

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 does not mention prerequisites, context, or any sibling tools (like 'bulk_create_company_webhooks_triggers_v2_0' or 'bulk_create_project_webhooks_triggers_v2_0'), leaving the agent with no usage direction.

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