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 'Bulk Create Materials' which implies a write operation, but does not disclose behavioral traits such as required permissions, whether it's idempotent, rate limits, error handling, or what happens on partial success. The HTTP method (POST) hints at creation, but lacks critical details for safe invocation.

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 no wasted words, consisting of a single line that includes the tool name, category, and endpoint. It is front-loaded with the core action. However, it is overly terse, missing necessary explanatory content, which slightly reduces its effectiveness despite efficient structure.

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 complexity of a bulk creation tool with no annotations and no output schema, the description is incomplete. It fails to explain the scope of 'bulk', expected input format for the array, success/error responses, or system behavior. This leaves significant gaps for an agent to operate safely and effectively.

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 descriptions for both parameters: 'project_id' as a unique identifier and 'time_and_material_materials' as an array of Material objects. The description adds no parameter semantics beyond the schema, but the schema itself is well-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 'Bulk Create Materials. [Project Management/Field Productivity] POST /rest/v1.0/projects/{project_id}/materials/bulk_create' restates the tool name ('Bulk Create Materials') and adds only the HTTP method and endpoint path. It lacks a specific verb+resource explanation and does not distinguish from sibling tools like 'create_material' or other bulk operations. This is a tautology with minimal added value.

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, constraints, or compare it to similar tools like 'create_material' or other bulk operations in the sibling list. Without any usage context, an agent cannot make informed decisions.

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