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 of behavioral disclosure. The description mentions 'PATCH' which implies a write/mutation operation, but doesn't specify what 'sync' entails—whether it creates, updates, or deletes tasks, what permissions are required, or what side effects occur. The '(Legacy)' tag hints at deprecated status but isn't explained. This leaves critical behavioral traits undocumented.

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 but inefficiently structured. 'Sync tasks' is under-specified, and the bracketed API path information is tacked on without clear integration. While not verbose, it fails to front-load essential information, making it less helpful than a truly concise description would be.

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 implied by a synchronization tool with an 'updates' array parameter, no annotations, and no output schema, the description is severely incomplete. It doesn't explain what synchronization means, what data is synchronized, the expected format of updates, or the result of the operation. For a mutation tool with no structured safety or output information, this description leaves too many gaps.

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 both parameters (project_id and updates) having descriptions in the schema. The tool description adds no additional parameter semantics beyond what the schema provides. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, though the description could have clarified the structure or purpose of the 'updates' array.

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 'Sync tasks' is a tautology that restates the tool name without adding clarity. It lacks a specific verb and resource definition, and does not distinguish this tool from its many siblings (e.g., other sync_* tools like sync_budget_line_items, sync_calendar_items). The bracketed text '[Project Management/Schedule (Legacy)] PATCH /rest/v1.0/tasks/sync' provides some context but is poorly integrated and doesn't clearly explain what the tool does.

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?

There is absolutely no guidance on when to use this tool versus alternatives. The description provides no context about prerequisites, appropriate scenarios, or distinctions from other synchronization tools in the sibling list. This leaves 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.