searchSpotify

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 usefully reveals that podcast queries match title, description, and publisher, which is beyond the schema. However, it omits other behavioral traits such as result ordering, authentication requirements, or rate limits, leaving a moderate gap for a read-heavy tool.

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 two sentences long and front-loads the primary function. The second sentence efficiently adds podcast-specific nuance without redundancy. Every word contributes to understanding.

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 combined with the complete input schema covers the essential context for a search tool: what it searches, the parameter types, and the special behavior for podcasts. It lacks explicit mention of output shape or pagination beyond schema, but the overall picture is sufficiently complete for an API search function.

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?

The schema covers 100% of parameters, providing baseline 3. The description adds meaningful value for the 'type' parameter, explaining specific use cases for 'episode' and 'show' that go beyond the enum labels. Other parameters are handled adequately by the schema.

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 the tool searches for six specific content types on Spotify, using the specific verb 'Search' and naming the resource. It distinguishes itself from sibling tools by comprehensively covering all Spotify searchable content types, while siblings focus on individual albums, playlists, or playback actions.

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 provides clear usage guidance, explicitly suggesting when to use 'episode' (find individual podcast episodes by topic/guest) versus 'show' (find podcast series), and explains matching behavior for podcasts. It does not explicitly contrast with sibling tools, but the domain is obvious given the tool's purpose.

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