Energy Market Overview

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds valuable behavioral context: results are account-specific, grouped by category, include 24h changes, support filtering, and 'dataset access varies by account entitlement.' No contradiction with the annotations.

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?

Five concise sentences, each earning its place: what it returns, when to use it, grouping/changes, filtering, access caveat, and alternative tool. Key information is front-loaded and the text is free of redundancy.

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 tool with one optional enum parameter and no output schema, the description is complete: it explains the return grouping, the 24h change context, the account-entitlement caveat, and routes to the sibling tool when more specific data is needed. Nothing critical is missing.

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 category parameter is fully documented in the schema. The description only says 'Supports filtering by category,' which adds little beyond the schema. Baseline 3 is appropriate because the schema carries the semantic weight.

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 verb and resource: 'Get the current prices returned by the API for this account in one call.' It clearly defines scope (broad market snapshot, grouped by category with 24h changes) and explicitly distinguishes itself from opa_get_price by naming the single-commodity alternative.

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?

It explicitly says when to use: 'when the user wants a broad market snapshot or asks about overall energy prices.' It also provides the key alternative and condition: 'For a single commodity, use opa_get_price instead.' This gives an agent clear routing guidance.

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