sok_tabell

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

No annotations are provided, so the description must disclose behavior. It states it uses a bundled index and returns 'most relevant' results with tabell_id. However, it does not specify what happens on no results, whether results are ranked, or any limitations beyond 'Search English titles.'

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?

Two concise sentences. The first sentence states the action and scope, the second explains the purpose and usage with sibling tools. No unnecessary words.

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?

Given no output schema, the description should detail the return format beyond just tabell_id. It does not mention whether titles, scores, or other fields are returned, leaving the agent uncertain about how to select among results.

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% with descriptions for all three parameters. The description adds context by linking 'emne' to list_emner and clarifying the query parameter's use, but much of the semantic information is already in the schema.

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 it searches the StatFin database by keyword, returns relevant tables with tabell_id for use in hent_tabell/hent_data. It distinguishes itself from siblings by explicitly naming them as consumers of the output.

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 explains the tool's unique local matching approach and that it is the only way to search (PxWeb has no server-side search). It names sibling tools, providing context for when to use this versus others, but lacks explicit 'when not to use' statements.

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