search_tracks

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

With no annotations, the description carries the full burden, and it does disclose the concrete HTTP endpoint and a quota indicator ('Quota: 🟢 single'), which is genuinely useful behavioral context. However, it does not mention rate limiting, whether the operation is strictly read-only, how pagination combines limit/offset/max_results, or any caching/history side effects.

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?

Two compact sentences with zero waste: the scope is front-loaded, the endpoint is parenthetical, and the quota is separated as its own clause. Every word 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?

The schema is rich and fully self-documenting, which compensates for the terse description. But with no annotations and no output schema, the description does not cover selection criteria among the many track-search siblings or describe expected results, leaving an agent to guess about behavior that the schema cannot convey.

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 documents all 7 parameters including defaults and enums. The description adds no parameter-level meaning, so it meets the baseline 3 but does not exceed it.

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 specific verb and resource ('Search tracks only') and adds the exact endpoint (GET /search?type=track), which pins down the API contract precisely. The 'only' qualifier distinguishes it from search_albums, search_artists, search_playlists, etc., though it leans partially on the tool name and does not explicitly name a sibling.

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 explicit when-to-use guidance, no exclusions, and no reference to alternative tools. Given the enormous sibling set containing many overlapping track-search tools (search_advanced, search_by_isrc, search_saved_tracks, search_market_diff, catalog_batch_lookup), the description leaves all routing decisions to inference.

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