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

Annotations already indicate this is a mutating, idempotent, non-destructive operation. The description adds valuable behavioral detail beyond the annotations: it costs 1 credit per call, and responses are temporary download links valid for 15 minutes. It does not contradict the 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 compact and front-loaded: the core purpose is stated first, the read/write mode switch follows, and cost/return details are separate and brief. Every sentence earns its place with no filler.

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 rich schema and annotations, the description covers the main operational details: mode selection, credit cost, and the temporary download link. A small gap remains: it is not entirely explicit whether the read mode returns metadata values directly or also returns a download link, since the return-link sentence could be read as applying only to the written PDF.

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%, so the schema already documents all parameters. The description adds the key behavioral distinction that omitting metadata fields triggers a read while supplying any field triggers a write, but it does not add substantial per-parameter meaning beyond the schema.

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 operation: read or write PDF metadata, and enumerates the exact fields involved (title, author, subject, keywords, creator, producer, dates). It does not explicitly contrast itself with sibling PDF tools like extract_pdf_text, but the 'metadata' scope makes the purpose unambiguous.

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 gives clear conditional usage: with no metadata fields supplied it reads; with any field supplied it writes. It provides clear context for when each mode applies, though it does not explicitly state when to prefer another sibling tool over this one.

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