Analyze Net Load

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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint false. The description adds useful behavioral context beyond those annotations: the calculation is hourly, defaults to wind and solar, allows selecting renewable fuels, and produces average, peak, and minimum net load values. This helps the agent understand the tool's output shape and configurable behavior.

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?

A single sentence packs the action, resource, formula, defaults, and output statistics without redundancy. The most important information is front-loaded, and every clause earns its place.

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?

With an output schema provided and read-only annotations covering safety, the description supplies the core calculation logic, defaults, and output metrics. The main minor gap is that 'CSD' is not explained, but this is a domain acronym rather than a missing behavioral requirement. Overall, an agent has enough to understand what the tool computes and how to invoke it.

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 documents start and end semantics, but renewable_fuels has no description. The description partially compensates by indicating that renewable generation is selectable and defaults to wind and solar, but it does not specify accepted fuel values, string formats, or how the request object maps to the calculation. Parameter semantics are therefore adequate but incomplete.

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 a specific verb ('Calculates') and clearly identifies the resource and formula: hourly Alberta Internal Load minus selected CSD renewable generation, with wind and solar as defaults. It also lists the computed statistics (average, peak, minimum), which distinguishes it from generic load or generation retrieval tools among the siblings.

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 this tool is for net-load analysis after subtracting renewable generation, but it gives no explicit when-to-use guidance, no conditions, and no mention of alternatives. An agent can infer the purpose but is not told when to choose this over get_load, get_generation, or other analysis tools.

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