get_shows

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

Discloses partial failure handling ('failures captured per item') and a limit on episodes per show. However, with no annotations, it does not state whether the operation is read-only, destructive, or any authentication requirements.

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?

Single sentence that conveys core purpose and key details without extraneous words. Front-loaded with the main action.

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, so return values are covered. However, the description does not clarify what 'values' expects (e.g., show IDs, URLs), nor does it reference siblings to help the agent distinguish use cases. Adequate but not comprehensive.

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 description must compensate but only mentions 'max_episodes' in passing. The 'values' parameter (likely show IDs) is not explained, nor is the format or source of valid values.

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 it fetches multiple shows, specifies the 'max_episodes' limit per show, and mentions failure capture per item. Distinguishes itself from singular 'get_show' and 'get_episode' as a batch operation.

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 explicit guidance on when to use this tool versus alternatives such as 'get_show' for a single show or other batch tools like 'get_tracks'. Usage is implied but not detailed.

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