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

The annotations already establish that this is a read-only, non-destructive operation. The description goes further by scoping results to the 'public music catalog' and warning not to infer ownership, licensing, or unpublished availability. This adds meaningful behavioral context about the tool's limitations that the annotations do not carry.

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 just two sentences. The first sentence front-loads the purpose and usage condition; the second adds a concise and valuable caution. No words are wasted.

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 one-parameter search tool with read-only annotations and an output schema, the description provides the essential context: what catalog is searched and what the results do not indicate. The only noticeable gap is the lack of explicit query parameter semantics, which is already reflected in the parameter_semantics score.

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 schema has zero description coverage for the query parameter, and the description does not explain what the query should represent (e.g., keyword, song title, artist). It only states the overall action of searching the catalog, leaving the description to infer the parameter's meaning from the tool name. This fails to compensate for the absent schema descriptions.

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 clear verb and resource: 'search the public music catalog'. This function is obviously distinct from sibling getters (get_track, get_release) and list_releases, as it is the only search operation. The wording is specific and not a tautology of the title.

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 sentence 'Use this when an agent needs to search the public music catalog' gives an explicit trigger condition for invocation, which is clear context. However, it doesn't explicitly name exclusions or alternative tools for when a specific known item is needed, so it doesn't earn a 5.

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