get_show

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

No annotations provided. The description adds the behavioral detail that the tool fetches a show 'with episodes', but does not disclose more (e.g., pagination, error handling, rate limits). Some context is given, but not comprehensive.

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 10-word sentence that is front-loaded and efficient. Every word earns its place.

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 has 2 parameters with no descriptions, no annotations, but includes an output schema. The description mentions 'with episodes', which helps a bit, but lacks parameter details and usage context. Given the sibling tools, it is minimally 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%, and the description does not clarify what the 'value' parameter expects (URL, URI, or ID?) or the purpose of 'max_episodes'. The description adds no meaning beyond the schema.

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 uses a specific verb ('Fetch') and resource ('podcast show with episodes') and clearly states the lookup keys (URL, URI, or ID). It distinguishes from sibling tools like get_episode (which fetches a single episode) and get_shows (which fetches multiple shows).

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 like get_shows or search. The description implies usage for fetching a single show by identifier, but does not mention exclusions or prerequisites.

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