health

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

The annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds only 'via Regionalstatistik' which hints at the data source but does not disclose behavioral details like response format, pagination, or data freshness. No contradiction with annotations.

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 extremely brief (one sentence), which might appear concise but omits critical information. It is front-loaded with the main purpose but lacks structure such as parameter explanation or usage nuance. The brevity sacrifices completeness.

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 tool's simplicity (1 required parameter, no output schema) and the large set of sibling tools, the description is incomplete. It does not clarify what the slug represents, how to obtain it, or what the output contains. An agent cannot reliably use this tool without external knowledge.

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 description coverage is 0%, meaning the description does not document the 'slug' parameter at all. The description fails to explain what a slug is or how it relates to the city or hospital directory, leaving agents without essential context to correctly invoke the tool.

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 the tool provides a hospital directory for a city via regional statistics. It indicates the resource (Krankenhausverzeichnis) and an implicit action (list/retrieve), but it does not explicitly name the verb. However, it is sufficiently specific to convey the tool's purpose.

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?

No guidance is provided on when to use this tool versus its many siblings (e.g., accidents, events). There is no context about prerequisites, typical scenarios, or exclusions. The description is purely declarative.

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