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 mentions 'Bulk Create' and a POST endpoint, implying a write operation, but doesn't disclose behavioral traits like permissions needed, rate limits, idempotency, or what happens on partial failures. The endpoint path suggests it's for timecard entries in a project, but this is inferred, not explicitly stated.

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 action ('Bulk Create'), followed by context and endpoint. It avoids unnecessary words, but could be more structured (e.g., separating purpose from technical details). However, it's efficient and doesn't waste space.

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 mutation tool with 2 parameters, the description is incomplete. It lacks details on behavioral aspects (e.g., side effects, error handling), usage context, and output expectations. The endpoint hint adds some value, but overall, it's insufficient for a bulk creation operation in a project management system.

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 'project_id' and 'timecard_entries' (including a maximum of 25 entries). The description adds no additional parameter semantics beyond what the schema provides, such as format details for the array items. Baseline 3 is appropriate given the schema does the heavy lifting.

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 Create' which indicates a creation action, but it's vague about what is being created. It adds '[Project Management/Field Productivity]' and a POST endpoint, which hints at context but doesn't specify the resource clearly. It doesn't distinguish from sibling tools like 'bulk_create_timecard_entries' or 'bulk_create_time_and_material_timecards', leaving ambiguity.

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 is provided. The description lacks any context about prerequisites, constraints, or comparison to sibling tools (e.g., 'bulk_create_timecard_entries'). This leaves the agent without direction on appropriate usage scenarios.

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