srgssr_audio_get_shows

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, which cover the behavioral profile. The description adds a small note about audio catalogs often containing podcasts, but no additional details on auth, rate limits, or side effects.

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 concise with a clear main sentence, use_case and important_notes tags, and an example. It uses XML-like tags effectively, though the example could be integrated more naturally.

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?

Given the presence of an output schema and annotations, the description does not need to detail return values. However, it lacks mention of pagination parameters (page_size, page) which are part of the input. The important note about podcasts adds value, but overall completeness is adequate but not thorough.

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?

The description does not explain the parameters beyond an example (business_unit='srf'). The input schema covers the parameters well, but with schema description coverage at 0%, the description should compensate more. The example is helpful but insufficient for a tool with three parameters including pagination.

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 it lists all radio shows for a given SRG SSR business unit, using a specific verb and resource. It implicitly distinguishes from sibling tools that deal with episodes, livestreams, or video content.

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 provides no explicit guidance on when to use this tool versus alternatives like srgssr_audio_get_episodes or srgssr_video_get_shows. The use_case tag is generic ('Katalog-Browsing') and does not help with selection decisions.

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