get_arbeidsgiveravgift

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

With no annotations, the description carries the burden of disclosing behavioral traits. It includes the auth requirement, which is beneficial, but does not describe the output format, whether it returns all zones, or any rate update/recency details. This is a moderate level of transparency for a simple read-only tool.

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, front-loaded with the primary purpose and followed by the auth note. Every word contributes, with no redundancy or unnecessary detail.

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 the tool's simplicity (no parameters, no output schema), the description covers the essential elements: what it gets, the organizing dimension, and access requirements. It could be more explicit about returning rates for all zones, but this is inferable from the absence of parameters and the phrase 'rates by geographic zone.'

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, so a baseline of 4 is appropriate. The description does not imply any parameter, and 'by geographic zone' accurately describes how the data is organized in the response rather than a filter input. No mismatch with the empty 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 the tool retrieves employer social security contribution rates by geographic zone, using a specific verb 'Get' and a distinct resource. It differentiates from sibling tools like get_mva_satser and get_skattesatser by naming the exact contribution type.

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 provides useful context by noting 'No authentication required,' which clarifies that the tool can be used without credentials. However, it does not explicitly mention alternatives or when-not-to-use, though the purpose is specific enough for an agent to infer appropriate usage.

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