Get Load

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

Annotations already declare read-only and idempotent behavior. The description adds useful context: timezone (America/Edmonton), interval boundary semantics ([start, end)), and a maximum range of 90 days. This goes beyond the annotation coverage and helps the agent understand constraints and result interpretation.

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 three short sentences, each adding distinct value: purpose, optional forecast, and time/range constraints. It is front-loaded and free of fluff, maintaining high readability and zero redundancy with the schema.

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?

For a read-only data retrieval tool with a rich output schema and comprehensive annotations, the description covers all essential context: what data is returned, units, timezone, interval boundaries, range limit, and optional forecast. No critical missing information is apparent for correct invocation and interpretation.

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 already has detailed parameter descriptions for start, end, and include_forecast, covering inclusivity and timezone interpretation. The description adds only the 90-day maximum range as new parameter-related information. Since schema coverage is 100%, the description contributes minimal additional semantic value.

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 Alberta Internal Load (AIL) observations in MW with an inclusive start and exclusive end interval. It specifies the resource (load), the unit (MW), and the time boundary, which distinguishes it from sibling tools like get_pool_prices or get_generation.

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 clearly implies usage for retrieving load data with optional forecast inclusion. It does not explicitly list alternatives or exclusions, but the context of sibling tools makes the use case clear. The 90-day max range and timezone note provide practical usage constraints.

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