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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful context beyond that: account scoping, newest-first ordering, and the non-generative nature of the call. It stops short of defining 'recent' (how many episodes, any window, pagination), which is the main behavioral unknown for a list operation.

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 short sentences, front-loaded with the scope and ordering, and the disambiguating negation is placed last where it does the most work. No filler wording.

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 zero-param read tool with full annotation coverage, the definition covers purpose and ordering adequately. But with no output schema, the description could have stated the result size or episode fields returned, and 'recent' is left undefined, so the agent cannot predict result shape or volume.

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 tool takes zero parameters, so there is no parameter meaning for the description to add beyond the schema. Baseline for a no-param tool applies, and nothing in the description misleads about inputs.

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 gives a specific verb and resource ('List recent daily episodes for this account') plus an ordering guarantee ('newest delivery date first'), so the agent knows exactly what it returns. It does not name a sibling such as get_episode for single-episode retrieval, leaving the list-vs-fetch distinction implicit.

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 one explicit exclusion — 'This does not generate an episode' — which rules out a plausible misread of the name. However, there is no positive guidance on when to prefer this over get_episode for a single episode, nor any alternative named.

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