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 states the tool exports to PDF but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires specific permissions, if it generates a file download, or any rate limits. The description is minimal and lacks essential context for safe invocation.

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 one sentence stating the purpose and including the API endpoint. There's no wasted verbiage, and the information is front-loaded. However, it could be more structured by separating the functional description from the technical endpoint reference.

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 no annotations, no output schema, and a mutation-like operation (export to PDF), the description is incomplete. It doesn't explain what the output is (e.g., a file URL, binary data, or job status), error conditions, or side effects. For a tool that likely generates files, this lack of context is significant.

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 5 parameters. The description adds no additional parameter semantics beyond what's in the schema. The baseline score of 3 is appropriate since the schema does the heavy lifting, but the description doesn't compensate or clarify parameter interactions.

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 the tool exports email communication to PDF, which is a clear verb+resource combination. However, it doesn't distinguish this tool from any potential sibling export tools (though none are listed in the provided siblings). The description is somewhat vague about what exactly gets exported beyond 'email communication'.

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. There's no mention of prerequisites, constraints, or comparison with other export or PDF generation tools. The agent must infer usage 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.