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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value by defining what a 'prisfall' is (kroner saved relative to the previous price), which is behavior beyond the structured fields, but it says nothing about the time window, data freshness or ranking order, leaving gaps for a data-listing 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?

A single front-loaded sentence with no filler — the core output description and the metric definition come first. It is efficient, though the extreme terseness borders on under-specification rather than tightness.

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 read-only listing with one optional parameter and no output schema, an agent can call it correctly, but the definition omits the ranking window and freshness of the 'registered' price drops. Given the absence of an output schema, a little more about what the returned entries represent would be warranted.

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?

There is a single optional parameter ('antall') and the schema documents it at 100% coverage with type, default and min/max bounds. The description adds no further meaning about how the count affects the result, so the 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 names the resource and the operation's output (the largest registered price drops in Norwegian webshops) and defines the ranking metric, so an agent knows exactly what it returns. It does not, however, distinguish itself from the siblings prishistorikk, sjekk_pris or sok_produkter, so the agent must infer the boundary itself.

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?

No when-to-use instruction, no prerequisites, and no reference to any alternative tool is given. The agent gets no explicit criteria for choosing this over prishistorikk or sok_produkter.

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