Create PDF Export For A Prime Contract

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

Adds value beyond annotations by mentioning zone restrictions and async job handles. However, includes a misleading statement about creating prime contracts, which reduces transparency.

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?

Description is concise and front-loaded with purpose. However, it includes redundant phrases like 'Procore API (v2.0)...' that could be omitted without loss of clarity.

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?

Mentions return type and zone limitation, which is good given no output schema. But the misleading statement about creating prime contracts undermines completeness and could confuse the agent.

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 covers all parameters with descriptions (100% coverage). The description lists required parameters but adds no extra semantic meaning beyond the schema, meeting baseline.

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 clearly states it creates a PDF export for a Prime Contract, with specific verb and resource. It differentiates from sibling tools by specifying the target contract type.

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 notes zone limitations (US01, US02) and what the tool returns (download URL or async job handle). It implicitly sets expectations for when to use, but does not explicitly exclude other scenarios.

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