searchSpotify

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose any behavioral traits such as result ordering, whether it requires authentication, rate limits, or caching. It only describes query matching for podcasts, leaving most operational behavior undocumented.

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?

Efficient two-sentence structure that front-loads the primary action and item types. The second sentence adds podcast-specific guidance without excessive verbosity, though it could be slightly tighter.

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 description covers the main search scope and provides podcast-specific guidance, which is helpful. However, for a search tool with no annotations and no output schema, it omits important behavioral details like authentication requirements, result ordering, pagination behavior beyond the offset param, and what fields are returned, leaving gaps an agent might need.

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 four parameters thoroughly, including enum values, limit/offset ranges, and query matching fields. The description adds some podcast-specific meaning but largely repeats what the schema provides, making the baseline 3 appropriate.

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?

States a specific verb (Search) and resource (tracks, albums, artists, playlists, podcast episodes, shows) on Spotify. The enumeration of item types and the podcast-specific matching fields clearly distinguish it from sibling retrieval tools like getAlbums or getMyPlaylists, which list rather than search.

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?

Provides clear usage context for the podcast types, explicitly routing the agent to type 'episode' for individual episodes by topic/guest and 'show' for series. However, it does not state when to use this search vs alternatives like browsing saved items, and no exclusions are given.

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