Get Generation

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds useful behavioral context: historical data is limited to wind and solar, and renewable share formula is provided. This extra context goes beyond annotations, though it doesn't cover error cases or output format specifics.

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?

Three concise sentences, front-loaded with the main purpose, then clear usage instructions. No wasted words; every sentence adds necessary information.

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 simple structure (one nested object with two optional parameters) and the presence of an output schema, the description fully covers the essential behavior. It explains both modes and the renewable share metric, making it complete for an 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?

The schema already covers the parameters well with a description of the request object, including the date range behavior. The tool description adds the renewable share formula and clarifies that historical data is hourly wind/solar, which enriches parameter meaning beyond schema.

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 'Returns Alberta generation data' and differentiates two modes: current fuel-mix snapshot vs historical wind and solar generation. This specific verb+resource combination distinguishes it from sibling tools like get_load or get_pool_prices.

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 instructs when to omit or provide start/end parameters, and even explains the renewable share calculation. However, it does not explicitly mention alternatives or when not to use this tool, hence not a perfect 5.

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