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

With no annotations, the description carries the full burden. It discloses that the tool lists 'indexed' laws, indicating a read-only operation and a constraint on which laws are returned. However, it does not mention output format, exhaustiveness, pagination, or any side effects. For a simple list tool, this is adequate but lacks rich behavioral detail.

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, concise sentence that front-loads the action ('List') and resource with examples. Every word earns its place, and there is no redundancy or filler.

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 no-parameter, no-output-schema listing tool, the description provides the essential information: what is listed and the relevant domain. It could optionally mention output details (e.g., alphabetical order or list format), but the tool's simplicity makes the description sufficiently complete.

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 zero parameters, so the description does not need to explain parameter semantics. The baseline for 0 parameters is 4, and the description adds context about what is being listed, which is sufficient.

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 function: 'List indexed German federal laws relevant to financial regulation' with specific examples (KWG, WpHG, GwG, ZAG). The verb 'List' and resource 'German federal laws' are specific, and the scope distinguishes it from siblings like de_law_lookup or uk_legislation_search.

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 implies the use case (listing German financial regulation laws) but does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions. The context is clear, but there is no guidance on when not to use it, unlike the high-calibration example which explicitly named an alternative.

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