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

Beyond the readOnly/non-destructive annotations, it discloses that rendering happens in a server-side browser, that there is a hard cap of at most 6 slides per call, and that layout_warnings are returned alongside the images. It does not explain failure modes (e.g., rendering timeouts, what happens if a slide id is out of range), and the return payload is partly covered by the output schema.

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?

Densely packed with the essential facts (output type, renderer, cap, selection rule, width, warnings) and front-loaded with the core purpose. The sentences are long and slightly run-on, with a small amount of restatement of the schema's width behavior.

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?

For a read-only rendering tool with a full output schema and full schema coverage, the description covers purpose, limits, and selection behavior adequately. It leaves a gap only around how this relates to the sibling layout-check tool and around error conditions.

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 100%, so parameters are already documented; the description adds precedence semantics not in the schema — that the 6-slide limit takes the first entries of slide_ids or of the from_number..to_number range, and that slide 1 is the default. That selection-order detail is genuinely useful and goes past the schema text.

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 gives a concrete verb and resource ('Pictures (PNG) of slides ... drawn by a browser on the server') and immediately frames the output as a visual rendering, which separates it from sibling readers like get_slides or check_layout. It also states what the pictures are useful for, so the agent knows it is not just another slide-metadata call.

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?

It gives a clear use condition: verify that text fits its blocks, blocks don't overlap, and the slide 'looks right' — i.e., visual QA where structural checks are insufficient. It does not, however, mention the obvious alternative check_layout or when that cheaper option should be preferred over rendering PNGs.

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