Find Price Events

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

Annotations already provide read-only, idempotent, and non-destructive hints. The description adds useful behavioral context: threshold can be absolute or percentile (default 90th), output includes event boundaries, duration, peak/average price, and load context 'when available', which clarifies variable output completeness. This goes beyond annotation defaults without contradicting them.

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, tight paragraph of three sentences. The primary purpose is front-loaded, followed by threshold logic and output summary. Every sentence adds necessary information with no filler or 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?

The tool has moderate complexity (nested request object, multiple parameters) and an output schema exists. The description provides a high-level overview of functionality, threshold mechanisms, and output elements, covering the essential aspects. It does not detail timezone handling or exact event definition, but these are addressed in the schema. Given the presence of output schema, the description is sufficiently complete for an agent to understand the tool's purpose and key behaviors.

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 schema already documents each parameter (start, end, percentile, min_duration_hours, threshold_cad_per_mwh). The description adds minimal new meaning: it restates the threshold options and default, which is also in the schema. It does not elaborate on interval semantics beyond schema, so it adds little value beyond the structured definitions.

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 detects sustained high Pool Price events over a specified interval, a specific verb-resource pair. It differentiates from siblings like get_pool_prices (raw prices) and compare_market_periods (comparisons) by highlighting event detection and output summarization.

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?

Usage context is implied: the description explains what the tool does (detect events) but does not explicitly state when to use it versus alternatives or mention exclusions. There is no reference to sibling tools for raw price retrieval or other functions, leaving the agent to infer appropriate use from the purpose.

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