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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds genuinely useful behavior: unpublished episodes are never returned and an empty query yields the newest episodes, which is scope behavior not encoded in annotations. It stops short of describing pagination edge cases beyond the return shape.

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?

Front-loaded with purpose, then defaults, then args, returns, and examples in a clean layered structure. The Args block largely restates the schema descriptions, which is mild redundancy, but the examples and exclusion line earn their space.

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?

An output schema exists, so the return values need not be explained, yet the description still sketches them usefully. Combined with the exclusion note and examples, an agent has enough to call and route this tool correctly; only deep pagination semantics are left implicit.

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 100%, so baseline is 3. The description adds cross-tool meaning by tying thema_id to bk_search_topics and clarifying that query matches the title specifically, plus the natural-language examples map queries to parameters. Marginal but real value over 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?

States a specific verb and resource ('Sucht in den veroeffentlichten Folgen des Podcasts Biohacking Kompakt') and distinguishes itself from siblings by naming bk_get_podcast_episode-like granularity and explicitly excluding bk_get_topic use cases. An agent can immediately tell this is an episode-search tool.

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?

Explicitly states the no-query default (newest episodes), gives three worked examples mapping natural-language questions to parameter settings, and names a concrete exclusion ('Nicht benutzen fuer: den Sachstand zu einem Thema (dafuer bk_get_topic)'). This is routing guidance, not inference.

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