Discover Spotify Podcasts

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable behavioral details: it caps results at 10 per type, returns typed results (shows vs episodes), and provides canonical Spotify links. This goes beyond the annotations without contradicting them.

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, front-loaded sentence with zero wasted words. It states the action, scope, result cap, result types, and link format efficiently.

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 tool is simple, and an output schema exists, so return values are covered structurally. The description fully captures the core behavior and constraints. It could mention pagination via offset, but given the output schema and simplicity, it is sufficiently complete.

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 for parameter meanings. It hints at the limit's cap ('at most 10') but provides no explanation for the query parameter beyond the verb 'search', and completely omits the offset parameter. The parameter names are self-explanatory but the description does not add sufficient detail for a schema with no descriptions.

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 Spotify shows and podcast episodes together, which is a specific verb+resource combination. It distinguishes itself from siblings like spotify_search by emphasizing the combined search of both podcast content types, and from spotify_podcast_show/episode by covering both in one call.

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 gives clear context: use this when you want to search both shows and episodes simultaneously. It does not explicitly mention alternatives or exclusions, but the 'together' phrasing implies a specific use case that differentiates it from single-type podcast tools.

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