SSB: slå opp gyldige koder for én variabel

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

Since no annotations are provided, the description carries the full burden for behavioral transparency. It discloses the core behavior (returns code/text pairs, supports filtering) and source/license, but it does not mention pagination, match type, ordering, or potential errors. The read-only nature is implied though not explicitly stated.

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 compact, front-loaded with the main function, and includes a useful example. The source/license line is additional context but not wasteful. Every sentence contributes value.

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 lookup tool, the description is fairly complete: it states what it does, gives an example, and notes the optional filter. It lacks explicit return-format details and how to identify the table, but the schema references 'tabell_info' for the variable code and sibling tools provide context.

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?

The schema covers two of three parameters ('søk' and 'variabel'), and the description adds the 'Halden' example and the concept of a single variable. However, the required 'tabell' parameter has no description in either the schema or the tool description, leaving an important semantic gap.

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 that the tool returns code/text pairs for one variable in a table, with optional text filtering. The concrete example of finding Halden's municipality code before fetching data distinguishes it from sibling tools like ssb_tabell_data and ssb_tabell_info.

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 'Bruk den til å finne f.eks. kommunekoden for Halden før du henter tall' gives a clear use case and tells the agent when to use the tool (before retrieving data). However, it does not explicitly mention alternatives or when not to use it, so it falls short of the highest bar.

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