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 states 'Show Calendar Item' and includes an HTTP GET method, implying a read-only operation, but doesn't explicitly confirm safety (non-destructive), discuss authentication needs, rate limits, error conditions, or the format of returned data. The '(Legacy)' tag hints at potential deprecation or outdated behavior, but this is vague. For a tool with zero annotation coverage, this minimal description leaves critical behavioral traits unspecified.

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 and front-loaded with the core purpose ('Show Calendar Item'), followed by domain context and the API endpoint. There's no wasted verbiage, and it efficiently conveys the tool's essence in a single line. However, the inclusion of the full API path might be overly technical for some users, slightly reducing clarity for non-technical agents.

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 (a read operation with required IDs and pagination parameters), lack of annotations, and absence of an output schema, the description is insufficient. It doesn't explain what a 'Calendar Item' contains, how pagination works with the 'page' and 'per_page' parameters, or what the tool returns. For a tool that likely retrieves structured data, this omission leaves the agent guessing about the result format and usage nuances.

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., 'Unique identifier for the project' for project_id, 'Calendar Item ID' for id). The description adds no parameter-specific information beyond what the schema provides. Since the schema does the heavy lifting, the baseline score of 3 is appropriate—the description neither compensates for gaps nor adds meaningful semantic context.

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 Calendar Item' is a tautology that restates the tool name without adding meaningful context. It mentions the API endpoint path and includes '[Project Management/Schedule (Legacy)]', which provides some domain context, but fails to specify what action is performed (e.g., retrieve, display details) or what a 'Calendar Item' represents. Compared to sibling tools like 'list_calendar_items' or 'create_calendar_item', it doesn't clearly differentiate its specific 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a specific project_id and id), nor does it contrast with sibling tools like 'list_calendar_items' (for listing multiple items) or 'update_calendar_item' (for modifications). Without any usage context, an agent must infer everything from the tool name and parameters alone.

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