get_genre_profile

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

readOnlyHint=true already establishes this as a safe read. Beyond that, the description usefully discloses the breadth and nature of returned content (touchstones, modes, progressions, mix targets, theory notes), which is real added context. It omits any note on auth, rate limits, or fallback behavior for unknown genres.

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?

It is front-loaded with the core purpose, which is good, but the remainder is a long comma-separated enumeration that reads as a run-on list rather than a structured summary. Appropriately scoped for a comprehensive tool, but could be tighter.

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 carries the return-value burden and does so by listing the content categories returned. Combined with readOnlyHint covering the safety profile, an agent has enough to call it correctly, though it lacks return-format or unknown-genre handling detail.

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 50%; the 'key' parameter is documented in the schema and 'genre' is self-evident. The description reinforces 'key' by noting progressions are 'spelled in a key' and references 'favourite keys', but adds no syntax or format detail (e.g., 'C', 'F# minor') beyond what the schema already conveys, so baseline 3 is 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 clearly states the tool retrieves everything about a genre and enumerates the specific content areas (history, tempo, harmony, groove, production, etc.), which is a specific verb+resource. It does not explicitly contrast itself against siblings like list_genres or get_instrument_notes, so it stops short of full differentiation.

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 only implied: an agent infers you call this to learn about a genre before composing or producing. There is no explicit when-to-use/when-not guidance and no named alternative (e.g., list_genres vs. this profile fetch), though the mention of 'ready for add_genre_groove' hints at a workflow link.

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