get_trygdeavgift

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 adds the behavioral context that 'No authentication required', which is valuable beyond the name. As a 'Get' operation, it implies read-only behavior, and the description gives sufficient transparency for a simple lookup, though it does not describe response format or edge cases.

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 a single sentence that front-loads the key information (what it gets, for which income types) and adds the auth note. Every word earns its place, with no redundancy or irrelevance.

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 no-parameter, read-only tool with no output schema, the description provides the essential context: purpose, scope, and authentication requirement. It is sufficiently complete for an agent to select and invoke the tool correctly, though it could optionally hint at the response format.

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 the baseline is 4. The description mentions income types, which are data dimensions rather than parameters, but this still helps set expectations for the returned data. No parameter explanation is needed since the schema is empty.

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 'Get social security contribution (trygdeavgift) rates' with a specific verb and resource, and further specifies the scope by income type (wage, self-employed, pension). This distinguishes it from sibling tools like get_skattesatser and get_mva_satser.

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 implies when to use the tool (when trygdeavgift rates are needed) and provides useful context about the income types covered. It does not explicitly mention alternatives or exclusions, but the scope is clear enough for an agent to select it appropriately among similar rate-lookup tools.

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