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 only states 'Show Item Response Set Response' and includes an API endpoint, but does not disclose behavioral traits such as whether it's a read-only operation, requires authentication, has rate limits, or returns paginated data. The endpoint hint ('GET') suggests a read operation, but this is not explicitly stated in the description.

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 under-specified, consisting of a tautological phrase and an API endpoint. While it avoids verbosity, it lacks essential information about the tool's purpose and usage. The structure is not front-loaded with actionable details, making it inefficient despite its conciseness.

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 (5 parameters, no annotations, no output schema), the description is incomplete. It fails to explain what the tool returns, its behavioral context, or how it fits among sibling tools. Without annotations or output schema, the description should provide more context, such as the nature of the response data or typical use cases, which it does not.

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 (e.g., 'Unique identifier for the company', 'Checklist Item Response Set ID'). The description adds no additional parameter semantics beyond the schema. Since the schema coverage is high, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 Item Response Set Response' is a tautology that restates the tool name without clarifying the action. It adds '[Project Management/Inspections]' as context and the API endpoint, but fails to specify what the tool actually does (e.g., retrieve a specific response within a response set). It does not distinguish from sibling tools like 'list_responses_in_the_specified_item_response_set' or 'show_response'.

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, context, or compare it to sibling tools (e.g., 'list_responses_in_the_specified_item_response_set' for listing multiple responses or 'show_response' for a generic response). This leaves the agent without usage direction.

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