get_show_episodes

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

No annotations are provided, so the description carries full burden for behavioral traits. It only describes parameters (limit, offset, market) but does not disclose pagination behavior, error handling, authentication requirements, or what the response contains. The output schema exists but is not referenced.

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 front-loaded with the purpose statement and uses a structured Args list. It is concise but not elegantly minimal—the parameter descriptions could be integrated more succinctly.

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?

With an output schema present, return values are not needed. Parameters are explained, but the description lacks context about tool behavior (e.g., what happens with invalid show_id or market filtering) and does not differentiate from sibling list tools.

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 compensates well. It adds value beyond the schema by specifying the numeric range for limit (1-50), the fact that market is an ISO code, and the default values for limit and offset. The schema only had titles and defaults.

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 "Get episodes of a Spotify show." which is a specific verb+resource. It distinguishes from sibling tools like get_show (which retrieves the show itself) and get_episode (single episode).

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 implies usage for listing episodes but provides no explicit guidance on when to use this tool versus alternatives like get_episode or get_show. No prerequisites or exclusions are mentioned.

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