List PDF Template Configs

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

The description adds significant behavioral context beyond the annotations: it details pagination behavior ('page and per_page control pagination and the response reports how many pages remain'), return format (JSON array), and failure modes (401/403/404). It reinforces the read-only nature, consistent with annotations.

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 a single dense paragraph that front-loads the purpose and then efficiently covers usage, defaults, return format, error handling, and API reference. Every sentence adds value with no fluff.

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 tool with no output schema, the description covers the return format, pagination tracking, error scenarios, and the API endpoint. Combined with the parameter-rich schema and annotations, it provides a complete picture for an 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 coverage is 100%, so the baseline is 3, but the description adds meaning: it explains company_id defaulting from procore_set_config and pagination parameter behavior. This goes beyond the schema's basic descriptions, though the 'Required parameters: company_id' phrase slightly conflicts with the earlier statement that it defaults when omitted.

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 opens with 'Returns a list of PDF template configs,' clearly identifying the action and resource. It further states its purpose as discovery and ID lookup before calling other tools, though it does not explicitly name or contrast with sibling tools.

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?

It explicitly states when to use: 'Use this to discover PDF template configs or to look up the id of one before calling a tool that needs it.' It also notes the company_id defaulting behavior via procore_set_config, providing clear context. However, it does not mention when not to use or alternatives.

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