Hent tall fra en tabell

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

With no annotations, the description must carry behavioral disclosure. It reveals that omitted dimensions are summed when possible and otherwise cause SSB to reject the query, and that `latestPeriods` is a shortcut. However, it does not describe the output format, error handling, or potential side effects, leaving gaps.

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 three sentences: purpose, prerequisite with selection semantics, and a parameter shortcut. Each sentence earns its place and is front-loaded with the main purpose, though it is slightly dense.

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?

The tool has a nested object and 4 parameters; the description explains the complex `selections` and `latestPeriods` well, but omits any mention of the return format or error behavior. With no output schema, this is a notable gap for a data-fetch tool.

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 50% of parameters; the description compensates by explaining the `selections` object structure, the wildcard `["*"]`, and the omission behavior, plus the meaning of `latestPeriods`. `maxRows` and `tableId` are self-explanatory from schema constraints, so the added value is solid.

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 fetches numbers from a table with explicit per-dimension selections, which is a specific verb and resource. It also references running `table` first to get valid codes, implying a clear distinction from the metadata sibling.

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?

It explicitly instructs to run `table` first to see valid codes, and explains how to use `selections` and `latestPeriods` with concrete semantics. It does not mention alternatives for data fetching beyond `latestPeriods`, but the prerequisite and parameter usage guidance is strong.

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