spotify_search

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

With no annotations, the description carries the full burden of disclosure. It does not mention that the tool is read-only, requires authentication, or any other behavioral traits. The description is silent on side effects, rate limits, or response format.

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 a single short sentence, which is efficient. However, for a tool with 6 parameters, it could be expanded without sacrificing conciseness. It front-loads the essential purpose well.

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?

Given the tool has 6 parameters, no output schema, and no annotations, the description is grossly insufficient. It fails to explain pagination (limit, offset), market filtering, authentication (bearer_token), or query syntax. The description does not satisfy the needs of an agent.

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 low (17%); only the 'type' parameter has a description. The tool description adds no additional meaning to the parameters beyond listing content types, which mirrors the 'type' parameter. The critical 'query' and 'bearer_token' parameters lack any semantic help.

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 clearly states it searches Spotify for specific content types (tracks, albums, artists, playlists). It uses a specific verb and resource, and distinguishes from sibling tools that target single items (like spotify_get_track).

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?

No guidance is provided on when to use this tool versus alternatives like spotify_get_track or spotify_get_artist. It does not mention prerequisites, such as requiring a bearer token, or when to use other search-related tools.

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