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

Annotations already declare this as a safe, read-only, idempotent, open-world read, so the safety profile is covered. The description adds useful context – the changelog nature of the data and that every entry carries a verifiable source – but the only operational detail (default limit 10) is essentially restated from the schema, and nothing is said about ordering or pagination behaviour.

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 prose is tight and front-loaded: what the changelog is, then the kinds of entries, then example queries. The trailing Args block partly duplicates fields already in the schema, which is minor waste but does not obscure the core message.

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?

With an output schema present, return values need no explanation, and all seven parameters are optional, so the agent needs only purpose and filtering semantics – both supplied. Enumerating the change categories plus example queries makes this comfortably callable, with only sibling-routing 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 71%, so several parameters are documented structurally (typ enum, seit pattern, response_format, thema_id). The description adds one genuine clarification – query searches 'Titel und Text' – but otherwise mostly restates the schema's own limits and defaults for limit/offset, whose schema entries carry no description text.

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 states a specific resource (the content changelog of biohackingkompakt.de) and enumerates exactly what kind of entries it contains – new peer-reviewed studies, retractions, failed approvals, case law, own corrections – each with a verifiable source. That is far more specific than a tautology. It never names a sibling (e.g. bk_search_inhalte) that an agent might confuse it with, so it stops short of full differentiation.

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?

Two concrete example questions ('Was ist neu bei Retatrutid?', 'Welche Bewertungen wurden zuletzt korrigiert?') give an agent clear context for when this tool is the right choice. However, no explicit when-not condition or named alternative (such as bk_search_inhalte or bk_search_studien) is provided, leaving overlap resolution to inference.

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