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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: results are scoped to a single case and reflect what the publication itself has linked, which tells the agent this is a curated set rather than an exhaustive index. It says nothing about ordering, pagination, or what happens when a case has no associated media.

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?

One sentence, zero redundancy, and the media-type enumeration is placed where it does the most work. Nothing is buried or padded.

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 single-parameter, read-only, closed-world lookup with a fully documented schema and no output schema, the description covers purpose and scope adequately. A brief note on ordering or empty-result behavior would close the remaining gap, but nothing essential to correct invocation is missing.

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 coverage is 100%: the single 'slug' parameter is typed, pattern-constrained, described, and its provenance ('from search_cases') is stated in the schema itself. With one fully documented required parameter, the description needs to add nothing, and it correctly does not waste words on 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 states a specific verb ('List') and a specific resource (media linked to a case) and enumerates the media types returned (documentaries, series, films, podcasts, books). An agent can distinguish it from search_media, which searches media rather than retrieving what a case links to. It stops short of naming the sibling tools it is not, so it is clear but not maximally differentiated.

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: call it when you already have a case and want its associated media. There is no explicit when-to-use or when-not guidance, and no sibling is named as an alternative for the overlapping 'find media' intent (search_media). The routing hint 'from search_cases' lives only in the schema, not the description.

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