Search releases

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 nothing behavioral beyond that: no default result ordering, no behavior when multiple filters are combined, no note that limit caps at 200, and no indication of pagination or result shape.

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?

One front-loaded sentence with no filler; the action and the searchable dimensions come first. It is terse to the point of omitting needed context, but nothing is 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 9-parameter, zero-required tool with no output schema and thin annotations, the description should explain how filters combine, default ordering, and what the limit applies to. It covers the filter surface at a minimum-viable level but leaves these gaps open.

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 only 22% across 9 params, and the description partially compensates by naming most facets (title, band, year range, type, genre, label, country) and clarifying that year is a range. But it adds no matching semantics (partial vs exact, case sensitivity) and ignores limit entirely.

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 (Search) and resource (releases) and enumerates the facets that can be matched. However, it never distinguishes itself from siblings such as search_bands, search_songs, or get_discography, so an agent must infer which search surface applies to a given query.

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 facet list implies what can be filtered, but there is no statement of when to use this over search_bands/get_discography, no note on prerequisite or combining filters, and no exclusions. Usage remains entirely inferred.

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