Get Generation

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds useful behavioral context: the current snapshot includes all fuels in MW, and renewable share is computed as wind+solar+hydro over total generation. It also notes historical data is 'where available' in the schema description. No contradiction with annotations.

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 concise, starting with the core purpose, followed by two distinct usage instructions, and a final note on renewable share computation. Each sentence adds value with no redundancy or filler. It is well-structured and 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?

The tool has an output schema, so return value details are handled separately. The description covers both invocation modes, the fuel scope, and the renewable share metric. Pagination parameters (limit/offset) are present in the schema and need no description. For a read-only data retrieval tool with clear modes, the description is complete.

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 description for the 'request' parameter already explains the two modes (without a date range vs with a date range). The tool description repeats this guidance, adding only the MW unit for the current snapshot. Since schema coverage is 100% and the description adds minimal new semantic detail beyond that, it meets the baseline but doesn't exceed it.

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 states 'Returns Alberta generation data' – a specific verb and resource. It then delineates two modes: current fuel-mix snapshot and historical wind/solar, making the tool's scope unambiguous. It does not explicitly name a sibling tool for differentiation, but the content is clear enough to distinguish from related tools like get_generation_capacity.

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 provides explicit instructions for the two invocation modes: 'Omit start/end for the current fuel-mix snapshot' and 'Provide start and end for historical wind and solar...'. This is clear context for using the tool itself. However, it does not mention alternatives among sibling tools or exclusions, so it lacks guidance on when to choose this tool over others.

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