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

Annotations declare readOnlyHint, idempotentHint, openWorldHint true and destructiveHint false. Description adds behavioral context that it returns real-time data with forecasts, but doesn't detail data source, timezone, or update frequency. 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?

Two concise sentences front-loaded with essential information (CAISO, real-time demand, forecast). No redundant words; every sentence adds value.

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 no output schema, the description adequately explains return values (demand series + forecasts). Annotations cover safety. Could mention data granularity explicitly, but overall complete for a simple read-only tool.

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?

Only one parameter 'limit' with description 'Latest N intervals (default 12).' Schema coverage is 100%, and the main description implies 5-minute intervals. The parameter description is adequate but doesn't add significant meaning beyond the 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?

Clearly states the tool retrieves CAISO real-time electricity demand vs. forecast for today, specifying return values (5-minute series, day-ahead and hour-ahead forecasts). Distinguishes from sibling tools like caiso_co2 and caiso_fuel_mix by focusing on demand.

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 lists use cases: 'is California load tracking forecast', peak-demand timing, demand-response triggers. While it doesn't mention when not to use, the specificity provides clear guidance for appropriate scenarios.

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