Get Pool Prices

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable context beyond annotations: timezone handling, the inclusive/exclusive interval semantics, and the maximum range, which informs expected response scope and avoids edge-case failures.

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 sentences, no fluff. The core function and interval are stated first, followed by the alternative usage and constraints. Every word earns its place, and the structure is front-loaded for quick scanning.

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 an output schema, so return format is not needed. The description covers the essential behavioral aspects (what it returns, interval, timezone, range, and alternative). It could mention pagination behavior, but that is documented in the schema via limit/offset, so completeness is adequate.

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?

Although schema already documents start/end inclusivity and timezone, the description adds the global range limit (366 days) and reinforces the interval syntax [start, end). With schema coverage at 100%, the baseline is 3; the added constraint and context justify a 4.

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 returns actual AESO hourly Pool Price observations in CAD/MWh for a specified interval. It also distinguishes itself from get_system_marginal_prices, which provides minute-level real-time pricing, so an agent can immediately tell them apart.

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 tells when to use the alternative (get_system_marginal_prices for minute-level pricing) and provides critical usage constraints: timezone (America/Edmonton) and maximum range (366 days). This leaves no ambiguity about when to select this tool over siblings.

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