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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's marginal contribution is its disclosure of what comes back: a season-by-season breakdown plus an 'up next' episode. That is meaningful output-shape context beyond the structured fields, though it omits whether unwatched-only or all seasons are returned.

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 well-formed sentence with the resource and the two returned artifacts front-loaded. No filler, no restatement of the title, and every clause carries information.

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 does the necessary work of sketching the return value (season-level progress and the next unwatched episode). For a two-optional-parameter read tool with full schema coverage and strong annotations, that is close to sufficient; only the shape of the season breakdown is left vague.

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 title and item_id are already fully documented, including the ambiguous-partial-match candidate behavior and the id-precedence rule. The description adds nothing further about parameter interplay, 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?

States a specific verb ('Read') and resource ('a TV show's season-by-season watch progress') plus a distinctive payload ('next unwatched episode / up next'). It implicitly separates itself from the mutating set_progress and from metadata-oriented get_details, though it never names those siblings explicitly.

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 only implied: the word 'Read' signals this is the non-mutating counterpart to set_progress, but there is no explicit 'use this when...' or pointer to get_details for metadata versus this tool for progress. An agent can infer the context but gets no stated exclusions.

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