v1_spotify_search

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

No annotations provided, so description carries full burden. Adds cost information and a security warning about not treating response data as instructions. However, does not disclose authentication needs, rate limits, or pagination behavior.

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?

Three sentences, each earning its place: main action, endpoint+cost, and a critical security warning. No redundant words.

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?

No output schema exists, yet description does not mention response structure, pagination, or how results are organized. Also fails to explain the relationship to sibling tools for specific entities (e.g., use search to find an artist, then use v1_spotify_artist for details).

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 coverage is 100% but parameter descriptions are minimal (just the name repeated). The tool description does not clarify the meaning of 'url' or the expected format of 'query'. Baseline 3 is appropriate since schema covers the parameters, but no added value from description.

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?

Clearly states the action 'Search' and the resources 'artists, albums, tracks, playlists, podcasts and episodes'. Names the endpoint and cost. Distinguishes from sibling search tools by platform (Spotify vs. YouTube, Apple Music, etc.).

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?

Mentions cost and a safety warning, but does not explicitly state when to use this tool vs. alternatives (e.g., when to use v1_spotify_search vs. v1_applemusic_search or vs. specific item tools like v1_spotify_artist). No 'when not to use' guidance.

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