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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond that: thema can be null when no topic is assigned, and if the episode does not exist or is not yet published, the response tells which episode numbers exist.

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 compact and well organized into Args, Returns, and Fehlerfaelle. The core behavior is front-loaded and every sentence contributes useful information without redundancy.

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?

For a single-episode getter, the description covers the input, the full return shape, the conditional null topic, and the invalid-number error behavior. Combined with the output schema and annotations, an agent has everything needed to call the tool correctly.

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 input schema already documents both parameters with types, enums, defaults, and descriptions, so schema coverage is 100%. The description's Args section mostly restates this and adds no meaning beyond the structured 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 first sentence states a concrete action ('Liefert eine einzelne Folge') with an exact resource: the 'Biohacking Kompakt' podcast. The nr argument makes clear this is a by-number retrieval, which distinguishes it from the sibling search tool bk_search_podcast.

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 use case is inferable: fetch a single known episode by number. However, the description never explicitly says when to prefer this over bk_search_podcast or bk_get_topic, nor does it provide any 'when not to use' guidance.

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