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

Annotations already cover read-only, idempotent, open-world, and non-destructive safety. The description adds a non-obvious data caveat: deliberately missing application, dosage, and experience sections for regulated topics, plus section-wise delivery.

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-loads purpose and uses Args/Returns structure. The Args and Returns blocks duplicate the schema and output schema somewhat, but the text remains compact and organized.

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 read-only page fetch with full annotations, an output schema, and 100% schema coverage, the description supplies key usage context, a return-shape preview, and the regulated-topic omission. Nothing essential for correct invocation is missing.

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 useful meaning for slug ('wie ihn bk_search_inhalte liefert', usually topic id) and abschnitt (matching part of the heading), beyond the schema examples.

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 ('Liefert') and resource ('vollstaendigen Text einer Seite von biohackingkompakt.de') and lists supported page types. However it does not explicitly contrast itself with get siblings such as bk_get_topic or bk_get_podcast_episode, so sibling differentiation is incomplete.

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 says the typical sequence is after bk_search_inhalte to read a find in context. No when-not guidance or alternative get tools are named.

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