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 'GET' which implies a read-only operation, but doesn't disclose pagination behavior, rate limits, authentication requirements, error conditions, or what the response format looks like. The description adds minimal behavioral context beyond the implied HTTP method.

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 extremely concise - just two phrases. It's front-loaded with the core purpose. However, the HTTP endpoint information could be considered extraneous since it doesn't help the AI agent understand when or how to use the tool. Every sentence earns its place, but more value could be added.

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?

For a list/read operation with 10 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'Bid Contacts' are, what the return format looks like, pagination behavior, or any constraints. The agent would struggle to use this tool effectively without additional context.

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 10 parameters thoroughly. The description adds no parameter information beyond what's in the schema. According to the rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in 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 states 'List Bid Contacts' which is a clear verb+resource combination, but it's vague about what 'Bid Contacts' are and doesn't distinguish from sibling tools. The bracketed context '[Preconstruction/Bid Management]' adds some domain context but doesn't fully clarify the purpose beyond the name.

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 about when to use this tool versus alternatives. The description doesn't mention any prerequisites, constraints, or sibling tools that might serve similar purposes. The HTTP method 'GET' is mentioned but doesn't constitute usage guidance.

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