get_database_stats

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool shows statistics, implying a read-only operation, but doesn't clarify whether it requires authentication, has rate limits, returns real-time or cached data, or what format the output takes. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence in German that directly states the tool's purpose and lists the statistics it provides. It's appropriately sized and front-loaded with the core functionality, with no wasted words or unnecessary elaboration.

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 complexity (simple read operation with no parameters), no annotations, and no output schema, the description is minimally adequate. It specifies what statistics are returned, which helps compensate for the lack of output schema, but doesn't address behavioral aspects like authentication or data freshness. For a no-parameter tool, it's complete enough to understand the basic purpose.

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 tool has 0 parameters, and schema description coverage is 100% (since there are no parameters to describe). With no parameters, the description doesn't need to add parameter semantics beyond what the schema provides. The baseline for 0 parameters is 4, as there's nothing to compensate for.

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's purpose: 'Zeigt Statistiken zur Datenbank' (shows database statistics) and specifies what statistics are included: 'Anzahl Einträge, verfügbare Jahre, Versicherer' (number of entries, available years, insurers). This is a specific verb+resource combination, though it doesn't explicitly differentiate from sibling tools like get_price_history which might also provide statistical data.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like compare_insurers or get_cheapest_insurers, nor does it specify contexts where database statistics are needed versus other data retrieval operations. Usage is implied but not explicitly stated.

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