Procore MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavioral traits. It only mentions 'Bulk Create' and an API endpoint, failing to describe that this is a write operation, potential side effects (e.g., creating multiple records), required permissions, error handling, or response format. This lack of information is critical for a mutation tool.

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 line with redundant information (repeating 'Bulk Create') and includes an API endpoint that adds little value for an AI agent. It is under-specified rather than concise, as it lacks essential details about the tool's function and context.

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 severely incomplete. It does not explain what 'equipment_timecard_entries' are, the expected array structure, success/error behaviors, or any operational constraints, leaving the agent unable to use the tool 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 parameter descriptions (e.g., 'Unique identifier for the project', 'Array of equipment timecard entries to be created'). The description adds no additional parameter semantics, but the schema adequately covers the basics, 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. [Project Management/Field Productivity] POST /rest/v1.0/companies/{company_id}/projects/{project_id}/equipment_timecard_entries/bulk_create' restates the tool name ('Bulk Create') and adds only a category label and API endpoint. It does not specify what is being created (equipment timecard entries) or the action's scope, making the purpose vague beyond the 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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools (e.g., 'bulk_create_timecard_entries', 'bulk_create_time_and_material_timecards'), there is no indication of distinctions such as resource type, context, or prerequisites. This leaves the agent without usage direction.

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