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

Annotations cover the safety profile (readOnlyHint). The description adds genuinely useful non-obvious context: precise pricing ($0.002 USDC per successful call via x402 on Base/Solana/Arc) and the important fact that failed calls are not charged. Data freshness (5-minute granularity, 'so far') is also disclosed.

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 dense sentence, front-loaded with what the tool returns and followed by pricing. Every clause carries operational meaning (data sources, granularity, forecast types, cost); nothing is filler.

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 present, the enumeration of returned fields in the description is somewhat redundant, but pricing and freshness fill the real gaps. For a zero-parameter, read-only, output-schema-backed tool, the agent has enough to call it 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 tool takes zero parameters, so the baseline is 4. There is nothing for the description to clarify about inputs.

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?

States a specific verb+resource: 'CAISO grid today, from its Today's Outlook data', then enumerates exactly which data streams are returned (5-minute generation by source, demand with forecasts, net load, peaks). This is clearly distinguishable from grid siblings like energy_ercot_texas_grid_status or energy_miso_midcontinent_iso.

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?

Usage is implied by 'today' and '5-minute intervals so far', so an agent can infer this is a current-day snapshot tool. However, no alternative is named for historical CAISO data or for other ISOs, and no when-not condition is stated.

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