Get access address by id

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral value beyond them by enumerating the returned fields and coordinate systems (EPSG:25832 and WGS84), which matters since there is no output schema.

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-loaded with the operation, followed by id provenance, return contents, a worked example, and sibling routing. Every sentence earns its place; only the enumerated field list is slightly long but justified by the absence of an output schema.

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?

With no output schema, the description compensates by listing the returned fields, and it documents the single required parameter's provenance plus an end-to-end example. An agent has everything needed to call it correctly.

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 coverage is 100% and the pattern is enforced there, so baseline would be 3. The description adds meaning beyond the schema by identifying the id as the same UUID DAWA uses for /adgangsadresser and giving a concrete example invocation with a real id and expected output.

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?

Specific verb+resource with a precise domain gloss ('husnummer: street + house number, the entrance') and explicit source (DAR). It distinguishes itself from siblings dar_get_address and dar_list_addresses by naming exactly what it returns and routing unit-listing elsewhere.

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?

Gives a clear alternative with condition: to list floors/doors at this entrance, call dar_list_addresses with the same id. Also clarifies the id is the same UUID DAWA used for /adgangsadresser, which helps an agent decide it can reuse an id from elsewhere. No explicit when-not guidance relative to dar_get_address or dar_get_street.

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