Create PDF Template Config

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

Annotations already indicate non-readonly, non-destructive. The description adds that the tool generates an export and returns a download URL or async job handle, which is important behavioral information beyond the annotations. No contradictions.

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, consisting of four sentences that each add value: purpose, usage, required parameter, and API endpoint. The second sentence has a minor typo ('Documents'), but overall it is well-structured and front-loaded.

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 tool has 5 parameters including a nested object and no output schema, the description covers the return type (URL or async handle) and API endpoint. However, it lacks details about the nested pdf_config_options and other fields, and doesn't clarify synchronous/asynchronous behavior beyond hinting at both. It is adequate but not exhaustive.

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 coverage is 100%, so the baseline is 3. The description only repeats the requirement for company_id, which is already in the schema. No additional parameter-level details or examples are provided.

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?

Clearly states it creates a new PDF Template Config for a company, generating an export and returning a download URL or async job handle. The verb 'create' and resource 'PDF Template Config' are explicit, and the tool is distinguished from sibling tools like list, update, and delete.

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?

Provides a usage statement ('Use this to create a new Documents in Procore') and mentions the required parameter. However, it does not explicitly specify when not to use this tool or suggest alternatives (e.g., update for existing configs). The guidance is present but minimal.

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