hent_data

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

With no annotations, the description discloses the API's size limit rejection behavior. It explains the structure of 'filtre' and special filters. Does not mention idempotency or side effects, but as a read operation, the critical behavioral trait (rejection at size limit) is covered.

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?

Description is concise: four sentences that front-load the purpose, then detail the key parameter with examples, and end with a critical constraint. No wordiness.

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?

Covers all parameters, special filter options, and a size constraint. Lacks an explicit description of the JSON-stat2 output structure, but given no output schema, the description is sufficiently complete for an agent to invoke 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 covers 100% of parameters, but description adds significant meaning: example of 'filtre' mapping, explanation of 'lang' enum, and source of 'tabell_id'. The description enhances the schema with real usage patterns.

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 starts with 'Fetch actual data values from a StatFin table as JSON-stat2', clearly stating the verb (fetch), resource (data values), and output format. It distinguishes from sibling tools like hent_tabell (metadata) and sok_tabell (search) by focusing on actual data retrieval.

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?

Provides explicit guidance: 'Omit filtre for the table's default selection' and 'Keep selections small — the API rejects queries over ~100 000 cells'. Special selections for 'top' and 'agg' are described. Could explicitly contrast with hent_tabell for metadata-only needs.

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