Calculate Capture Prices

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

Annotations already declare the operation as read-only, non-destructive, and idempotent. The description adds meaningful behavioral context beyond that: it identifies the data sources (hourly Pool Price, official CSD generation), the join operation, and the generation-weighting methodology, giving the agent a clearer model of what happens when invoked.

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 a single, well-structured sentence that front-loads the core action and data source. Every phrase adds information, with no redundancy or filler.

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?

Given the presence of an output schema and annotations covering safety, the description is largely adequate. It explains the data sources, the computation approach, and the available filter dimensions. Minor gaps remain around whether filters are optional and how results are grouped when both asset_ids and fuel_types are provided, but these are not critical.

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 0%, so the description must compensate. It does partially by explaining that filtering is by 'asset and/or fuel group,' which maps to asset_ids and fuel_types, and that the time window is required. However, it does not add details about accepted ID formats, fuel group values, or behavior when no asset/fuel filter is provided.

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 a specific action: joining hourly Pool Price to CSD generation and calculating generation-weighted capture price and capture rate. This distinguishes it from sibling tools like get_pool_prices and get_generation, which retrieve raw inputs rather than perform the analytic calculation.

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 implies when to use the tool — when capture prices/rates by asset or fuel group are needed — but it does not explicitly state exclusions or alternative tools. There is no direct guidance on when to prefer this over related calculation tools such as calculate_asset_energy_revenue.

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