list_genres

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

readOnlyHint=true already declares this as a safe read, so the description only needs to add context. It usefully discloses the breadth of each profile's contents but says nothing about result count, ordering, pagination, or whether filters are conjunctive.

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?

A single front-loaded sentence opening with the verb and resource, followed by a structured four-facet enumeration. Efficient, though the parenthetical lists are somewhat dense for the amount of actionable information conveyed.

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, the description does convey the shape of returned profiles, which is valuable. However, it omits how many genres are returned, their ordering, and how the four filters interact, leaving real gaps for a browse tool whose whole purpose is narrowing results.

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 description coverage is 100%, so all four optional filters (mode, tempo, family, search) are already documented in the schema with examples. The description adds no parameter meaning beyond that, making the baseline 3 appropriate.

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 and resource ('Browse the genre library') and explains what each genre profile contains across composition, rhythm, arrangement and mixing. It does not distinguish this enumeration from the sibling get_genre_profile, which an agent would need to choose between without opening a schema.

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, no mention of when to prefer this over get_genre_profile, list_scales or add_genre_groove, and no note on how the optional filters should be combined. All selection logic is left to the caller.

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