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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered and the description's lower bar is appropriate. The description does add two genuinely useful facts not in the annotations: a batch cap ("up to 8 at a time") and that the response includes measurer findings. These additions are valuable but cryptically phrased, and nothing is said about the shape of the rendered output or what happens when more than 8 slides are requested.

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?

Two short sentences with the core behavior front-loaded and no filler. The brevity is close to the point of under-specification, but nothing is redundant or padded.

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 carries responsibility for explaining the return value, and it only gestures at it via "what the measurer found." The batch limit is a helpful inclusion, but an agent still lacks a clear picture of what it receives back from a rendering call.

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 both document_id and slides are documented in the schema and the baseline of 3 applies. The description's only extra signal is the batch limit, which constrains the slides array but does not clarify ordering, error behavior for out-of-range slide numbers, or the cost of the call. That single clause does not meaningfully exceed 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?

"Draws slides for real and shows them to you" conveys that this renders slides visually rather than returning text, which is a meaningful distinction from deck_read_slide. However, "for real" is idiosyncratic and "the measurer" is undefined jargon, so an agent must infer that this produces a rendered image plus measurement diagnostics. It never names the sibling it replaces (deck_read_slide, deck_list_slides), leaving differentiation to guesswork.

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 explicit when-to-use or when-not-to-use guidance. The distinction between this and deck_read_slide or deck_list_slides — read the text vs. see the rendered output — is only weakly implied by "shows them to you." No prerequisites or follow-up actions are mentioned.

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