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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds real operational context beyond them: an API key is required, and the data granularity is five-minute MW demand. Rate limits and row-cap behavior are left to the schema.

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 tight sentences, front-loaded with the resource and unit, followed by usage cues and the auth requirement. No filler or repetition of schema content.

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 no output schema, the description usefully characterizes the returned data (MW demand at five-minute resolution for the New England footprint), and annotations carry the safety profile. It is slightly thin on return shape and volume, but adequate to call the tool 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?

Schema description coverage is 100% with three self-documented parameters, so the baseline is 3. The description's "Requires an API key" reinforces the _apiKey parameter but adds no semantics beyond what the schema already spells out (format, free-account URL).

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 resource (ISO New England system load / total electricity demand), unit (MW), and resolution (five-minute), plus the six-state footprint. An agent can separate this from isone_fuel_mix and isone_lmp by resource alone.

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?

Gives concrete usage contexts ("New England electricity demand right now", "ISO-NE peak load today", demand-response and capacity questions), which is clear when-to-use guidance. It stops short of naming alternatives such as isone_lmp or isone_fuel_mix or stating exclusions, so it is not a full 5.

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