Get Spotify Podcast Episode

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral caveats beyond annotations: 'Preview URL evidence may be absent and no full audio is returned.' This warns about possible missing fields and clearly scopes the output, which the annotations do not convey.

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?

Two sentences, zero waste. The first sentence states the core function, the second adds important caveats. Front-loaded and easy to parse.

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 simple one-param tool with a rich output schema and strong annotations, the description is nearly complete. It covers the main function, expected output type, and key limitations. It could mention how to obtain the episode ID (e.g., via other tools), but that is not essential for invoking this tool correctly.

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 coverage is 0%, so the description must compensate. It does state that the tool works 'for one exact Spotify episode ID', giving some meaning to episode_id. However, it does not specify the ID format, source, or how to validate it. The description adds minimal value beyond the parameter name.

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 states a specific verb ('Return') and resource ('typed metadata for one exact Spotify episode ID'). It clearly distinguishes this tool from siblings like spotify_podcast_show_episodes (which lists episodes) and spotify_podcast_show (show metadata) by emphasizing 'exact episode ID' and 'no full audio is returned'.

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 usage is implied: use when you have an exact episode ID and need metadata. However, it does not explicitly state when not to use it or point to alternatives (e.g., 'use spotify_podcast_show_episodes to discover episode IDs'). No clear exclusions or alternative guidance is provided.

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