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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the call is read-only, whether it mutates state, what permissions are needed, or what happens on a missing preview. The name implies a read but this is never stated.

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?

It is short, but brevity here comes from omission rather than economy. The single fragment is a label with an emoji rather than a front-loaded, informative statement.

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 annotations, no output schema, and an ambiguous parameter, the description must define what a preview is and what the call returns. It does none of this, so an agent cannot reliably decide to invoke it or predict its result.

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 nominally 100%, but the single 'detail' parameter's own description ('Parameters for this action (title, content, preview_id)') is opaque and lists fields that make little sense for a get operation. The tool description adds no clarification, leaving the parameter's real semantics unresolved.

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 'PDF Generator: get preview' essentially restates the tool name with a category prefix. It does not say what a 'preview' is, what resource it retrieves, or how it differs from siblings like preview_document or list_previews, making it a near-tautology.

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?

There is no guidance on when to call this tool versus preview_document, list_previews, or generate_pdf. No prerequisites, no context, no exclusions are stated anywhere.

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