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. It implies a read-only operation via the HTTP GET method and suggests retrieving a specific recycled near-miss by ID, but it doesn't clarify critical behaviors: whether authentication is required, if there are rate limits, what happens if the ID doesn't exist, or the format of the returned data. The description is too sparse to adequately inform the agent about how the tool behaves.

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 parts: a tautological statement and an API endpoint. However, it's not front-loaded with useful information—the key details (like it being a GET operation) are buried. While it avoids unnecessary verbosity, it under-specifies by omitting critical context, making it less effective despite its brevity.

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 complexity (retrieving a specific recycled incident), lack of annotations, and absence of an output schema, the description is incomplete. It doesn't explain what 'recycled' means in this context, what data is returned, or any error conditions. The agent is left with significant gaps in understanding how to use the tool effectively, especially compared to more detailed sibling tools.

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 input schema (e.g., 'project_id' as 'Unique identifier for the project', 'id' as 'Near Miss ID'). The description adds no additional semantic context beyond the schema, such as explaining relationships between parameters (e.g., that 'incident_id' might be optional or related). Given the high schema coverage, a baseline score of 3 is appropriate, as the schema adequately documents parameters without extra help from the description.

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 'Show Recycled Near Miss' is a tautology that restates the tool name without adding clarity. It includes a category tag '[Project Management/Incidents]' and an API endpoint 'GET /rest/v1.0/projects/{project_id}/recycle_bin/incidents/near_misses/{id}', which hints at a read operation for a specific recycled near-miss incident, but the purpose remains vague—it doesn't specify what 'show' entails (e.g., retrieve details, view metadata) or distinguish it from sibling tools like 'show_near_miss' or 'list_recycled_near_misses'.

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. It lacks any mention of prerequisites, context (e.g., when a near-miss is in the recycle bin), or comparisons to sibling tools such as 'show_near_miss' (for non-recycled items) or 'list_recycled_near_misses' (for listing multiple). This absence makes it difficult for an agent to decide when this tool is appropriate.

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