get_today_prices

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

No annotations are provided, so the description must fully disclose behavior. It states the tool returns 'all 24 hourly electricity prices', but lacks details such as whether prices are in order, the unit (e.g., DKK/kWh), or any timezone considerations. No mention of data source, update frequency, or potential delays.

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 extremely concise at two sentences. The first sentence states the core functionality and defaults, and the second provides a usage hint. There is no unnecessary text, and every word contributes meaning.

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 has 3 parameters with no output schema, so the description should partially compensate. It mentions 'all 24 hourly electricity prices' but does not specify the structure (e.g., list of objects with hour and price) or any units. This is adequate but leaves room for improvement.

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 description coverage is 100%, so the baseline is 3. The description does not add any extra meaning beyond what the schema already provides for each parameter (area, mode, date). The enums and defaults are well-documented in the schema, so the description offers no additional value.

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 gets all 24 hourly electricity prices for a given date in a price zone, and includes a specific use case hint: 'elpriser i dag / time for time'. This distinguishes it from sibling tools like get_current_price (single current price) and get_price_forecast (forecast).

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 provides explicit context with 'Use for "elpriser i dag / time for time"', indicating when to use it. However, it does not explicitly exclude other scenarios or mention alternatives like get_cheapest_hours, which could be used for filtering. The sibling names help but are not referenced.

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