ams_price

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

The readOnlyHint annotation already establishes that this is a safe read operation, so the description only needs to add context. It does add the currency unit (kr per kWh) and the temporal window (today, including next hours), but it says nothing about timezone, data freshness, or update cadence, which matter for a price feed.

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 short sentences with no filler, and the core purpose ('Electricity price by hour') is front-loaded ahead of the detail about what values are returned.

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 zero-parameter read tool with an output schema and readOnlyHint, the description is largely sufficient: it identifies the resource, the unit, and the time scope. Only freshness and timezone conventions are left unstated, which are minor gaps given the schema carries the return shape.

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 takes zero parameters, so there is no parameter semantics burden on the description. The baseline of 4 applies, with no missing input documentation to compensate for.

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?

It states a specific resource and content: hourly electricity prices, with the current price in kr per kWh, upcoming hours, and the cheapest remaining hours today. That is concrete enough to distinguish it from a plain 'current value' tool, though it does not explicitly contrast itself with siblings like ams_now or ams_history.

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?

Usage is only implied through the mention of 'cheapest hours left today', which hints at planning or cost-optimization purposes. There is no explicit statement of when to prefer this over ams_now or ams_history, and no exclusions or prerequisites are given.

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