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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds only one behavioral detail beyond that: the return payload is the complete HTML rather than a summary or image. It does not mention whether hidden elements, styles, or scripts are included.

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?

A single front-loaded sentence with no filler, which suits a simple read tool. It is on the edge of being too terse, but nothing is wasted.

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 simple, annotated two-parameter read tool with no output schema, the description is minimally sufficient and clarifies that the return value is HTML. It still leaves open how this differs from deck_look_at or deck_read_source when an agent is choosing how to inspect slide content.

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%, with both document_id and slide documented, including the 1-based slide numbering. The description adds no meaning beyond the schema, so the baseline of 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?

The description states a specific verb and resource: 'Reads the complete HTML of a slide.' An agent can immediately tell this is a read operation over slide markup, and 'complete HTML' distinguishes it from a rendered preview. However, it does not name or exclude siblings such as deck_read_source, deck_read_styles, or deck_look_at, so differentiation is left to inference.

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 when-to-use guidance, no prerequisite, and no alternative named among a large deck_* sibling set. The agent must guess whether this replaces deck_look_at or deck_read_source for inspecting a slide.

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