Genres

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a non-obvious conditional behavior — the synthetic 'later' genre only appears once the account has saved something to Listen later — which an agent could not learn from the schema or annotations and which prevents misreading an apparently missing genre.

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 resource and its fields, with no filler. The quoted 'later' phrasing is slightly cryptic but is the minimal way to flag the conditional genre.

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 simple no-arg read with no output schema, the description covers what is returned at a field level (ids, slugs) and the one conditional case. It stops short of saying whether results are ordered, complete, or paginated, which leaves a small gap for an agent consuming the list.

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; the baseline for a no-param tool applies. No false or confusing parameter claims are made.

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?

States a specific verb+resource ('All genres') and even the payload shape ('their ids and slugs'), which is more than the name alone conveys. It does not explicitly differentiate itself from the nearby get_genre_tracks sibling, but the catalog-vs-tracks distinction is inferable from the wording.

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 statement of when to call this versus alternatives such as get_genre_tracks, search, or get_home_section. The second sentence is a data caveat, not usage guidance, so the agent must infer the call context entirely.

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