search_skatteetaten

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

With no annotations, the description provides useful context: no authentication required and returns content from the most relevant public page. However, it does not explicitly state read-only behavior or potential rate limits, though search implies non-destructive.

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 sentences, direct, with no filler. The first sentence establishes the core functionality and the second adds return and auth context.

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 simple single-parameter search tool, the description covers purpose, return value, and auth. It could be enhanced with guidance on when to use this over specific data tools, but overall it is complete enough.

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 a clear parameter description ('Search query (Norwegian or English)'). The description adds no additional parameter semantics beyond the schema, so baseline 3 applies.

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 a specific action (search) on a specific resource (skatteetaten.no) for any tax-related topic, clearly distinguishing it from sibling tools that return specific data points or search persons.

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 use for general tax-related queries but does not explicitly compare with alternatives like get_skatteetaten_page or specific getter tools. No exclusions or when-not guidance is provided.

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