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

Beyond the annotations it discloses the payment mechanics (secure link, iDEAL or card, via Dodo Payments, EUR 2.95 incl. VAT) and the delivery behavior (report opens right after payment). This is exactly the behavioral context an agent needs before triggering a paid transaction and is not derivable from the 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?

Front-loads the outcome (payment link) and price, then the report contents, then the usage condition. The enumerated content list is long but each item is informative; structure is sound with little wasted text.

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?

No output schema exists, but the description explains the return value (a secure payment link) and the post-payment behavior, covering the important gaps. It is nearly complete, though it does not clarify how the free-text q parameter relates to the structured postcode/house_number options.

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 100%, so all five address parameters (q, postcode, house_number, addition, house_letter) are already documented in the schema. The description adds only the phrase 'on a Dutch address' and no extra syntax or precedence detail beyond the schema baseline.

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 verb (buy) and resource (the full address report), and itemizes exactly what the paid report contains. It is clearly distinguishable from the free sibling tools like nl_home_report and nl_home_basic.

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?

'Only use when the user wants the full report or asks to buy it' is an explicit usage constraint and exclusion, which is strong. It does not, however, name the specific free alternative tools an agent should route to otherwise, so it stops short of full routing guidance.

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