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 does add genuine behavioral context beyond the annotations — conditional output such as 'on cast v2 every character with full body and sheet' and 'cover_custom true when set_series_cover set it' — but says nothing about size, pagination of the episode list, or failure behavior for an unknown series_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?

It is compact and front-loads the most important payload items, so nothing is obviously wasted. However, it is an unpunctuated fragment with a parenthetical aside in the middle, which makes it harder to parse than a short declarative sentence would be.

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?

Since no output schema exists, describing the returned fields is the right instinct and this description does that reasonably well, including conditional fields. It is still incomplete for a tool with 40+ siblings: it omits the identifier parameter's semantics and any routing hint against the closely related series/overview/canon readers.

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?

There is one required parameter with 0% schema description coverage, and the description never mentions series_id, its expected format, or where an agent would obtain one. With the schema carrying no documentation, the description had the full burden here and did not take it.

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 enumerates the payload (premise, beat map, leads, locations, episodes, cover_url) which implicitly conveys that this retrieves a full series record, but it never states a verb or the resource explicitly — the sentence is a bare noun list with no main clause. It gives an agent a decent sense of what comes back, yet it does not cleanly distinguish the tool from get_series_overview, get_series_canon, or list_series.

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 at all: no statement of when to prefer this over get_series_overview (summary) or get_series_canon (canon state), and no exclusions or prerequisites. The agent must infer usage purely from the field list.

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