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

Annotations already indicate readOnlyHint: true and destructiveHint: false, so the description does not need to repeat that. Beyond annotations, it discloses that returned URLs are signed and expire after an hour, which is critical behavioral information not captured elsewhere. The description also notes it's read-only and spends no quota. It could be slightly more explicit about pagination behavior, but overall excellent.

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: starts with the core purpose, then explains when to use it, then provides behavioral details and return format. Each sentence adds meaningful content. Slightly verbose in the middle but not unwieldy.

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 only 2 optional parameters, a clear schema, and robust annotations, the description is largely complete. It explains the return format, URL expiration, and how to use with siblings. It lacks explicit mention of rate limits or whether the user needs specific permissions, but these are minor gaps.

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% for both parameters, so the baseline is 3. The description does not add significant meaning beyond what the schema already provides for the pagination parameters. It explains the overall use case but not parameter-specific nuances.

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 the tool lists documents produced by the account, newest first. It distinguishes itself from siblings like get_render by explicitly explaining its role in finding previously rendered PDFs whose URLs have expired.

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: when you need to find a PDF made in a previous turn, by a schedule, or by another process and the original URL has expired. It also mentions the alternative: use get_render with the id to mint a fresh URL.

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