SCB: hent tall fra en tabell

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

No annotations are provided, so the description carries the behavioral burden. It does disclose that output is ready-made labeled rows rather than raw json-stat, and gives source/license context, but it does not mention errors, size limits, or response structure. This is adequate but minimal.

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 and front-loaded with the main behavior and output format. The source/license sentence is not invocation-critical but is short and does not significantly bloat the description.

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 tool with no output schema and no annotations, this description leaves important gaps: the required 'sti' parameter is never explained, and there is no pointer to sibling tools for discovering table paths or variable codes. An agent would likely need to open related tools to call this 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 description coverage is only 50%, and the required 'sti' parameter has no description in either the schema or the tool description. The 'utvalg' parameter is well documented in the schema, but the description adds little beyond what the schema already states, and it fails to compensate for the undocumented required parameter.

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 operation ('Henter tall fra en SCB-tabell') and the output form ('ferdige rader med etiketter (ikke rå json-stat)'). It does not explicitly differentiate from closely named siblings like scb_tabell_verdier, but the output-format detail helps narrow the intent.

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 only guidance is 'Angi ett utvalg per variabel du vil begrense', which says how to filter but not when to prefer this tool over alternatives. With siblings such as scb_tabell_info and scb_tabell_verdier present, the absence of explicit routing guidance is a clear gap.

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