spotify_get_episode

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

No annotations provided. Description only states 'Get detailed information' which implies a read operation, but does not specify what fields are returned, whether it's read-only, or any potential side effects. Minimal behavioral disclosure.

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?

Under-specified single sentence; lacks critical details like parameter format and usage context. While short, it sacrifices necessary information, making it not appropriately sized for the schema and context.

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?

Output schema exists (not provided) but description fails to explain when this tool should be invoked relative to siblings (e.g., after searching or retrieving show episodes). Missing usage context despite low complexity.

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?

Single parameter episode_id has no description in schema (0% coverage) and description adds no context about format (e.g., Spotify URI/ID) or constraints. Completely relies on parameter title.

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?

Clearly states verb 'Get' and resource 'detailed information about a podcast episode.' Differentiates from sibling like spotify_get_show_episodes (which lists episodes) and spotify_get_saved_episodes (which returns saved episodes), though not explicitly.

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?

No guidance on when to use this tool vs alternatives. Does not mention prerequisites like needing an episode ID obtained from search or show listing, nor when to avoid this tool.

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