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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description reinforces the safety profile while adding new context the annotations cannot carry: 'costs nothing' (credit/cost impact) and an inventory of what is returned (hosts, voices, saved shows, rooms). It does not contradict the annotations.

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 and its contents, with usage guidance last. The first sentence is dense with a nested parenthetical definition, but every clause carries information an agent needs; nothing is padding.

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 and no parameters, the description shoulders the explanatory load and does so: it defines the entity, lists what is returned, states the cost and read-only nature, and places the tool in the create/reuse workflow. An agent can select and call it correctly with no further context.

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 nothing for the description to disambiguate; baseline 4 applies. The absence of filtering is consistent with an unfiltered 'everything the user has saved' list.

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 names the resource precisely and even defines domain jargon ('a studio is the picture of the two hosts at their desk that an Animated Podcast episode is built on'), then enumerates what each entry contains (hosts, voices, saved shows, empty rooms). It distinguishes itself from sibling preview_podcast_studio and links to create_podcast, though it is framed as a noun phrase and leans on the tool name for the 'list' verb.

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?

Explicit routing: 'Use before create_podcast when the user wants to reuse a studio or show, or to pick a room' gives a clear trigger condition. The reference to preview_podcast_studio draws rooms points at the adjacent tool, though it stops short of stating when not to call this instead.

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