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 'Delete' which implies a destructive mutation, but it doesn't disclose any behavioral traits such as whether deletion is permanent, requires specific permissions, has side effects, or returns confirmation. This is a significant gap for a destructive operation.

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, but it's not front-loaded with critical information. The first sentence is a tautology of the name, and the second adds API details without clarifying purpose or behavior. It avoids verbosity but under-specifies key details.

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 tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It fails to address critical aspects like confirmation of deletion, error handling, or what happens post-deletion. For a delete operation, this leaves the agent with insufficient context to use it safely.

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 ('Unique identifier for the project' and 'Lookahead Task ID'). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 given the high schema 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 states the action ('Delete') and resource ('Lookahead Task'), but it's vague about what a 'Lookahead Task' is and lacks sibling differentiation. It includes a category tag '[Project Management/Schedule (Legacy)]' and API path, which adds some context but doesn't fully clarify the purpose beyond the basic verb-noun pairing.

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 does not mention prerequisites, consequences, or any context for deletion (e.g., irreversible action, permissions required). It's a bare statement with no usage instructions.

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