List PDF Template Configs

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. The description adds value by stating the return format (JSON object with file contents or download URL) and mentioning pagination and filtering, which provides useful behavioral context beyond 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 well-structured with a clear sequence: return type, usage, return details, required parameter, API endpoint. It is mostly concise, though the API endpoint path at the end may be extraneous for an agent.

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 read-only list tool, the description provides necessary information: what it returns, how to use it, and required parameters. It mentions file contents or download URL but could be more specific about the response structure. Missing output schema, so description compensates adequately.

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% and each parameter has a description. The description does not add new meaning beyond the schema, only mentioning pagination and filtering in general. Baseline 3 is appropriate.

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 returns a list of PDF template configs, with specific verb and resource. It mentions enumeration, finding IDs, and filtering. However, it also refers to 'Documents' which may cause slight ambiguity about the exact resource 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 explicitly tells when to use this tool: for paginated overview, finding IDs, or filtering. It does not explicitly mention when not to use or list alternatives, but the context of siblings and the readOnlyHint make it clear this is for read operations.

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