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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior the annotations do not: the auth requirement ('Requires an API key') and the shape of the returned data (five-minute intervals, three price components, eight zones/hubs). It omits rate limits and pagination behavior, but given the no-output-schema situation this is solid added context.

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?

Front-loaded with the densest, most useful sentence, followed by usage triggers and the auth note. The second sentence ('ISO-NE runs the grid and wholesale market for CT, MA, ME, NH, RI and VT') is partly background that an agent does not strictly need to invoke the tool, but it is short and clarifies regional coverage.

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?

For a four-parameter, zero-required read tool with full schema coverage and no output schema, the description supplies the key missing pieces: data granularity, geographic scope, component breakdown and the auth prerequisite. Only pagination/return-format behavior is left implicit, which is a minor gap given the annotations cover safety.

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 date, limit, _apiKey and location_id all documented in the schema itself, so the baseline is 3. The description only indirectly touches parameters — the API-key requirement maps to _apiKey and the 'eight New England load zones and hubs' gestures at location_id — but adds no syntax or format detail 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?

States a precise resource — ISO-NE five-minute real-time locational marginal prices, broken into energy, congestion and loss components, for the eight New England load zones and hubs. The resource framing (prices, with sub-components) inherently distinguishes it from the sibling ISO-NE data tools isone_fuel_mix and isone_load, which cover generation mix and demand rather than prices.

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?

Provides explicit trigger phrases ('New England power price right now', 'Massachusetts wholesale electricity price', 'ISO-NE zonal price spread') that tell the agent when this tool applies. It does not, however, name the alternative ISO-NE siblings or state when NOT to use it, so routing between adjacent tools is left partly to inference.

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