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

No annotations are provided, so the description carries the burden of behavioral disclosure. It successfully conveys the scope ('Works for any music — not limited to the OnChain Music catalog') and lists the specific data returned. However, it does not mention edge cases (e.g., unknown genres), rate limits, or response format, leaving some transparency gaps.

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?

The description is three sentences, each serving a distinct purpose: (1) defines the output, (2) lists use cases, (3) clarifies scope. It is front-loaded with the core behavior and contains no redundant or filler content. Every sentence earns its place.

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?

Although there is no output schema, the description provides a clear list of output categories (BPM, song structure, instrumentation, etc.) and use cases. It covers the essential aspects for a simple lookup tool with two parameters. The only minor gap is not explicitly linking the 'include_sync_uses' parameter to the 'common sync use cases' output, but this is easily inferred. Overall, it is sufficiently complete for the tool's complexity.

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 the schema already fully explains both parameters ('genre' and 'include_sync_uses'). The description adds minimal parameter-related meaning beyond the schema—it only implies that 'genre' determines the conventions and that 'sync use cases' are part of the output. Since the schema handles the heavy lifting, a baseline score of 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's function: 'Returns music industry conventions for a given genre including typical BPM ranges, song structure, instrumentation, key tendencies, production characteristics, and common sync use cases.' It uses a specific verb ('Returns') and a distinct resource ('music industry conventions for a given genre'), which clearly distinguishes it from sibling tools like search_catalog or get_track.

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?

The description provides explicit use cases: 'Useful for songwriting, production decisions, A&R research, playlist curation, and sync licensing briefs.' This gives clear context for when to use the tool. However, it does not explicitly mention when not to use it or name alternative tools, so it falls short of a 5.

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