get_formuesskatt

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

No annotations are provided, so the description carries the full burden. It discloses one behavioral trait: 'No authentication required,' which is useful. However, it does not describe the return format, data currency, or other potential side effects. For a simple read-only lookup, 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 two sentences, with the primary purpose front-loaded. The second sentence adds the only necessary behavioral note (no authentication). No unnecessary words or repetition.

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 zero parameters and no output schema, the description covers the core purpose and authentication requirement. However, it could add context about the applicable tax year or data source to help an agent decide between this and a general tax-rate tool. Despite that, it is largely complete for its simplicity.

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 tool has zero parameters, and the input schema confirms an empty object. With no parameters to document, the description does not need to add parameter-level details. The baseline for zero-parameter tools is 4, and the description's content about rates and thresholds is sufficient.

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 states 'Get formuesskatt (wealth tax) rates and net wealth thresholds' – a specific verb plus a clearly identified resource. The parenthetical translation aids understanding and the resource is distinct from sibling tools like get_mva_satser or get_trinnskatt_satser, which focus on other tax types.

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 offers no guidance on when to use this tool vs. alternatives. It only mentions 'No authentication required,' which is a prerequisite, not a usage condition. There are no references to situations where another tool would be more appropriate.

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