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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: the links are authenticated, the operation performs no rendering, offline PDFs carry no access gate, analytics or live interactions — behavior an agent could not infer from structured fields.

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?

Three short sentences, front-loaded with what is returned, followed by the fallback rule and the scope caveats. No filler; every sentence carries distinct information.

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?

With no output schema, the description does the work of naming the key returned fields (directDownloadAvailable, browserPrintUrl) and the failure mode for direct download. The undefined term 'management links' and the absence of any error/not-found behavior are the remaining gaps, but the definition is sufficient to invoke 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?

The single `id` parameter has 0% schema description coverage, so the description must carry the burden. It implies the id identifies an owned page ('for an owned page'), which is useful, but never names the parameter, its format, or what happens for an unowned/nonexistent id.

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 — return authenticated browser-print, PDF-download and management links for an owned page — and explicitly disclaims what it does not do (render or publicly expose a PDF). No sibling tool in the list overlaps with PDF export, so disambiguation is inherently satisfied, and the negative framing removes a likely misinterpretation.

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?

Gives a clear conditional rule: use the direct download only when directDownloadAvailable is true, otherwise fall back to browserPrintUrl for Print / Save as PDF. This is concrete selection guidance for the returned artifacts, though it does not state when an agent should call this tool at all (e.g. versus get_page) or note ownership preconditions beyond 'owned page'.

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