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

No annotations are provided, so the description carries the behavioral burden. It discloses the key validation trait (elfproef) and the non-real-person guarantee, but omits output format, uniqueness behavior, and how count is applied.

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?

One sentence with no filler. The main action and constraint are front-loaded, and every clause adds meaningful information.

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 simple one-parameter generator, the description covers purpose, validity, and usage restriction. It falls short by not stating the output format or clarifying what count produces, especially given the absence of an output schema and annotations.

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% and the description never mentions the count parameter. The schema's name and constraints partially compensate, but the description adds no semantic guidance beyond what the structured schema already shows.

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 an action (generate), a resource (Dutch BSN test numbers), and a distinguishing property (pass elfproef but belong to no real person). This differentiates it from siblings like generate_test_iban and generate_brp_test_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 phrase 'For development and test data only' gives clear usage context and an implicit warning against production use. It does not explicitly name alternative tools or exclusion conditions, but the BSN-specific scope is enough for an agent to choose correctly.

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