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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context by specifying the shape of the payload — slide numbers, section markers, deep links, and ancillary resources — which tells an agent what it will get back without an output schema. It does not mention behavior for a nonexistent deck id.

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 dense sentence, front-loaded with the core concept ('Outline of one slide deck') and then listing returned artifacts. No filler, no repetition of the parameter name or schema content.

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 one required parameter, full schema coverage, and no output schema, the description carries the return-value burden well by enumerating the outline's contents. It is nearly complete; the only gap is what happens when the deck id is unknown or invalid.

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%, and the schema already explains the deck id format (file name without .html) and its source in list_decks. The description adds only the reinforcement that exactly one deck is in scope, so this sits at the baseline where the schema does the heavy lifting.

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 names a specific resource (one slide deck) and enumerates what the result contains: numbered titled slides, section markers, deep link, PDF, exercise repository, related articles. That is clearly distinct from get_article (single article) and list_decks (catalog). It falls short of 5 only because it is phrased as a noun phrase rather than a verb+resource statement.

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?

Usage is implied rather than stated: the schema note 'Deck id from list_decks' hints at the list_decks -> get_deck_outline workflow, and the singular 'one slide deck' signals this is the per-deck drill-down. But there is no explicit when-to-use/when-not guidance and no mention of when to prefer get_article for a single article surfaced in the outline.

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