get_skattesatser_index

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

With no annotations, the description carries the burden. It explicitly notes 'No authentication required', which is a useful behavioral disclosure. It also implies a read-only operation. However, it does not mention result structure, pagination, or any other behavioral details. For a zero-param index tool, this is adequate but not rich.

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 long, front-loaded with the primary purpose, and contains no redundant or irrelevant information. Every word serves a purpose.

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?

The tool is simple (0 params, no output schema), and the description covers purpose, useful context, and auth requirements. It falls short of describing the exact format of the returned index (e.g., list of links, topics), but this is not critical for a discovery tool. Overall, it is complete enough for an agent to use effectively.

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 input schema has zero parameters, so the description's meaning is essential. It explains what the tool does with no inputs, returning a full index. This adds context beyond the empty schema, warranting a baseline 4.

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 specifies the verb 'Get' and the resource 'full index of all rate pages on skatteetaten.no/satser/'. It also distinguishes this from sibling rate-specific tools by noting it is for 'discovering what topics are available', implying it returns a directory rather than actual rate values.

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 states 'useful for discovering what topics are available', which clearly indicates a use case: use this tool to explore the range of rate topics before querying specific rate tools. It does not explicitly name alternatives or exclusions, but the context is clear enough for a discovery tool.

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