Procore MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Bulk Create' and an API endpoint, implying a write operation, but fails to detail critical aspects like required permissions, whether it's idempotent, error handling, or rate limits. The endpoint hint ('POST') suggests mutation, but this is insufficient for safe agent 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 two sentences, front-loading the core action. However, the second sentence with the API endpoint and category tag adds clutter without enhancing clarity for an AI agent, slightly reducing efficiency.

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 inadequate. It lacks details on expected behavior, success/failure responses, and how to structure the 'time_and_material_timecards' array. For a mutation tool with significant implications, more context is needed for reliable agent use.

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 in the schema. The description adds no additional parameter semantics beyond the schema, such as format examples for the array items or constraints on 'project_id'. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 the action ('Bulk Create') and resource ('Time and material timecards'), but it's vague about what 'Time and material timecards' are and lacks specificity. It doesn't clearly distinguish from sibling tools like 'bulk_create_timecard_entries' or 'create_time_and_material_timecard', leaving ambiguity in scope and function.

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. The description includes a category tag '[Project Management/Field Productivity]' and an API endpoint, but these don't offer practical usage instructions, prerequisites, or comparisons with related tools like 'bulk_create_timecard_entries' or single-create operations.

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