search

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It simply says 'Search Spotify' and reveals nothing about response format, pagination, default behavior, side effects, rate limits, or whether it queries the Spotify API for catalog items. This does not satisfy 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 text is short, but this is under-specification rather than genuine conciseness. The single sentence conveys no actionable information beyond the tool name, and it is not structured in a way that surfaces key choices like type or pagination.

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 tool with three parameters, an enum, a default, and no output schema, this description is not nearly complete. An agent cannot safely know what this tool returns, how to scope results, or what constraints apply.

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 by explaining what query, type, and limit mean. The description contains no parameter information at all, leaving agents to rely entirely on the schema without added semantic context.

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, 'Search Spotify,' is essentially a restatement of the tool's name with only the Spotify resource added. It gives no indication of what is being searched (tracks, albums, playlists) and does nothing to differentiate this generic 'search' name from siblings like find_track or find_in_playlists.

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 description offers no guidance about when to use this tool versus alternatives. It does not mention the available entity types, the intended use cases, or when to prefer sibling tools like list_playlists or find_track.

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