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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that data is 'Retained in R2' and implies a large aggregate payload through its inventory, but it never states size, latency, or whether the response is expensive/truncated—the traits most relevant for a full-canon read.

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 sentences, front-loaded with the resource name and scope. The long parenthetical inventory is dense but each item carries information about what is returned.

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?

No output schema exists, so the description must convey return content, and it does so exhaustively via the cast/locations/episodes inventory. The remaining gap is the undocumented series_id parameter and no note on response size.

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?

The single parameter series_id has 0% schema description coverage, and the description never mentions it or its expected format. With coverage below 50%, the description is expected to compensate, and it does not.

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 resource ('Full series canon') and enumerates its contents in detail (cast, locations, casting progress, episode outfits, storyboard images, shots, line checks). It does not, however, differentiate from close siblings like get_series, get_series_overview, or get_episode_storyboard, which an agent would need to choose correctly.

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 prescriptive context: 'read before writing the next episode,' which tells the agent when this tool belongs in the workflow. It does not name alternatives or exclusions, so an agent comparing it to get_series_overview gets no explicit routing rule.

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