Kartverket: søk opp adresse

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

No annotations are provided, so the description must carry the full burden of disclosing behavioral traits. It only mentions the data source and license, not response format, pagination, rate limits, or error behavior. This is a significant gap for a tool with no structured 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?

The description is two sentences, front-loaded with the core function. The source/license line is additional but not critical for invocation; still, it is brief and does not waste words. Could be slightly more focused but remains appropriate in size.

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 search tool, the description covers the main purpose and output fields (postcode, municipality, coordinates). However, it lacks usage alternatives, limitations, and edge cases. With no output schema or annotations, it is minimally adequate but not comprehensive.

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 50% (only 'sok' has a description). The description mentions output fields but does not explain the 'antall' parameter or add any parameter-level semantics beyond what the schema already states. It fails to compensate for the missing 'antall' description.

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: 'Finner offisielle adresser med postnummer, kommune og koordinater' (Finds official addresses with postcode, municipality and coordinates). This specific verb+resource distinguishes it from siblings like kartverket_sted (place names) and kartverket_adresse_fra_punkt (reverse lookup).

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 usage for searching addresses but does not explicitly state when to use this tool versus alternatives like kartverket_adresse_fra_punkt or kartverket_sted. No exclusions or alternative comparisons are provided, so guidance is only implied.

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