Get Pool Prices

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

Annotations already declare readOnly, openWorld, and idempotent. The description adds valuable context beyond annotations: the timezone (America/Edmonton), the exclusive end interval semantics, and the maximum range. This is useful operational behavior not disclosed elsewhere.

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 concise sentences. The first establishes purpose, the second gives an alternative and critical constraints (timezone, range). No wasted words; information is front-loaded.

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 tool has an output schema, return format is covered. The description addresses interval semantics, timezone, range, and sibling differentiation. It is self-contained for an AI agent to select and invoke correctly.

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 coverage is 100%, with descriptions for start, end, and include_forecast. The description adds minimal parameter-specific semantics beyond the schema, though it implicitly clarifies that 'actual' observations are returned vs forecast. Baseline of 3 is appropriate since the schema carries the parameter documentation.

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' with a specific interval format [start, end). It distinguishes itself from the sibling get_system_marginal_prices by specifying hourly actuals vs minute-level real-time pricing.

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?

Explicitly provides an alternative: 'Use get_system_marginal_prices for minute-level real-time pricing.' Also sets a hard limit of 366 days, guiding appropriate usage. This is clear when-to-use vs. when-not-to-use guidance.

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