Procore MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It mentions a GET endpoint, implying a read-only operation, but does not explicitly state safety (e.g., non-destructive), permissions needed, rate limits, pagination behavior (though schema has page/per_page), or output format. The description lacks essential behavioral details for a tool with 17 parameters.

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 (one sentence fragment plus endpoint), which is efficient but under-specified. It front-loads the core action ('List Checklists') but wastes space on the API endpoint, which is less helpful for an AI agent. It could be more structured with purpose and usage guidance.

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 (17 parameters, no annotations, no output schema), the description is inadequate. It does not explain what 'checklists' are, how results are returned, pagination behavior, or error conditions. For a list tool with extensive filtering options, more context is needed to guide effective use.

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%, so the schema fully documents all 17 parameters. The description adds no parameter-specific information beyond implying filtering via the API path. Baseline is 3 because the schema does the heavy lifting, but the description does not compensate with any additional context about parameter interactions or filtering logic.

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 'List Checklists. [Project Management/Inspections] GET /rest/v1.0/checklist/lists' restates the tool name ('List Checklists') with minimal elaboration, making it tautological. It adds a category tag and API endpoint, but does not specify what 'checklists' are in this context or distinguish this tool from other list tools in the sibling set (e.g., 'list_checklist_inspections', 'list_checklist_templates').

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. With many sibling tools (e.g., 'list_checklist_inspections', 'list_checklist_templates'), there is no indication of how this tool differs—such as whether it lists checklist instances, templates, or something else. The agent receives no usage context.

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