Find Price Events

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable behavioral context: threshold may be absolute or percentile (default 90th), returns event boundaries, duration, peak/average price, and load context when available. This goes well beyond the annotations 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?

Two sentences, front-loaded with the main action and scope. Every clause delivers useful information without verbosity. No fluff 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?

Given the rich input schema and output schema, the description is complete. It explains the core purpose, threshold types, and what results are returned, which is sufficient for an agent to decide invocation and interpret basic outputs.

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?

The input schema provides 100% coverage of all parameters, so the description does not need to heavily compensate. It does mention threshold flexibility and the default 90th percentile, aligning with the schema, but it adds little beyond what the schema already states. Baseline of 3 is appropriate.

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 uses the specific verb 'Detects' with the resource 'sustained high Pool Price events' and clearly scopes it to a time interval in CAD/MWh. It distinguishes this from sibling tools like get_pool_prices (raw price retrieval) by focusing on event detection rather than simple data access.

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 usage by stating what the tool detects, and the context of 'events' over time makes the use case clear. However, it does not explicitly mention when to prefer this over related tools like get_pool_prices or get_market_snapshot, nor does it offer exclusion criteria.

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