search_music

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

No annotations are present, so the description bears the full disclosure burden. It implies a read-only search operation, but it does not mention behavior such as pagination, limit effects, result ordering, or the fact that search is restricted to tracks/artists beyond the filter parameter itself. This is minimal behavioral transparency.

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 extremely concise with no filler; both sentences earn their place and the key parameter hint is front-loaded. It borders on under-specification, but that issue is more relevant to contextual completeness than to conciseness.

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 annotations and only a one-sentence description, the tool is under-specified for confident use among 15 siblings. The output schema helps with return values, but the description still lacks usage context, query expectations, and behavioral details needed for a 3-parameter tool.

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 0%, so the description must compensate. It usefully explains the filter parameter's allowed values ('track' or 'artist'), which is the least obvious parameter. Query is reasonably inferable from its name, but limit receives no semantic explanation, so compensation is only partial.

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 operation ('Search') and resource ('Spotify'), and the filter line narrows the target to tracks or artists. It is understandable on its own, though it does not explicitly differentiate itself from sibling get_track or get_artist tools.

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 guidance about when to use this tool versus alternatives such as get_track, get_artist, or get_recommendations. No conditions, exclusions, or preferred use cases are given, so the agent must infer when search is appropriate.

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