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 mentions 'POST' implying a write operation, but doesn't disclose behavioral traits such as permissions required, whether it's idempotent, error handling, or what happens on success (e.g., returns a signature ID). The description lacks critical context for safe and effective use.

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: the tool name and an API endpoint. It's front-loaded with the action, but could be more structured by separating purpose from technical details. There's no wasted text, though it lacks completeness in conveying purpose clearly.

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 of a signature creation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It fails to explain the tool's role in a workflow (e.g., after a signature request), what the output looks like, or any side effects. This leaves significant gaps for an AI agent to understand how to use it correctly.

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 already documents all parameters (list_id, signature_request_id, project_id, attachment, attachment_string). The description adds no additional meaning about parameters beyond what's in the schema, such as relationships between them or usage examples. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Create Checklist Signature' which indicates a creation action on a checklist signature resource, but it's vague about what exactly is being created (e.g., a signature record, a signature image attachment). It doesn't distinguish from sibling tools like 'create_checklist_signature_request' or 'create_signature_for_time_and_material_entry', leaving ambiguity about its specific role.

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 on when to use this tool versus alternatives is provided. The description includes a category '[Project Management/Inspections]' and an API endpoint, but these don't offer practical usage context, prerequisites, or comparisons with related tools like signature request creation tools.

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