bag_lookup_address

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

Annotations already declare readOnlyHint=true and openWorldHint=true, which cover safety and data volatility. The description adds that it uses PDOK Locatieserver, providing source transparency, but does not elaborate on other behavioral traits like pagination, result limits, or rate limits. Minor added value over 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?

Extremely concise: two sentences with no wasted words. First sentence states purpose and data source; second lists search types. Front-loaded with key 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?

Moderate completeness: given 4 parameters, no output schema, and annotations that cover readOnly/openWorld, the description provides core purpose but lacks details on default rows (10), minimum/maximum, required parameters (none), and return format. Without output schema, some indication of result structure would help. Annotations partially compensate.

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 has 4 parameters with 0% description coverage. The description mentions 'free text, postcode, or house number', which maps to query, postcode, and huisnummer parameters, adding meaning beyond bare schema. However, it omits the rows parameter (page size) and does not explain parameter constraints, so compensation is partial.

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?

Description clearly states the tool looks up BAG address details via PDOK Locatieserver, and lists specific search methods (free text, postcode, house number). This distinguishes it from sibling tools like bag_address_detail (specific ID lookup) and bag_linked_data_select (linked 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?

No guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or comparison with bag_address_detail or other search tools. The description only states what it does, not when it's appropriate.

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