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

Beyond the annotations (which already cover readOnly/idempotent/destructive/openWorld), the description discloses truncation caps (1,000 bookmarks, 8 levels, `truncated`), named-destination resolution, error semantics (422 encrypted, 503 timeout, free of charge), latency, price, free-tier quota, and an untrusted-content warning. This is unusually rich behavioral context.

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?

Front-loads the verb, resource, and alternative in the first sentence, then layers limits, failure modes, cost, and a safety note compactly. The pricing/free-tier/docs tail is slightly over-stuffed but each element is actionable.

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?

Because an output schema exists, the return shape need not be spelled out, yet the description still orients the agent on the tree structure and truncation. Combined with limits, error codes, and timing, an agent has everything needed to call it correctly.

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% and defines the url vs pdf_base64 alternatives, so the schema carries the parameter burden. The description adds only a small note about page being 1-based and possibly referencing another file, which is return semantics rather than parameter guidance. Baseline 3 applies.

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?

States a specific verb and resource ('Read the bookmarks of a PDF as a nested tree') and explicitly names the counterpart tool pdf_set_outline for writing, so an agent can distinguish it from the write sibling without opening a schema.

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?

Explicitly routes the agent to pdf_set_outline when the goal is writing bookmarks, and notes that encrypted input must be unlocked first. It does not distinguish itself from other read-oriented siblings such as pdf_metadata or pdf_inspect, so guidance is clear but not exhaustive.

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