isone_load

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

Annotations declare readOnlyHint=true, and the description adds 'real-time 5-minute' and regional scope, which goes slightly beyond the annotation. However, it does not disclose limitations such as whether historical data is accessible, update frequency details beyond 'real-time', or any response format expectations, keeping transparency modest.

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?

The description is two sentences, the first stating exactly what the tool does with a leading verb and resource, the second giving necessary geographic context. No filler or redundant detail—every word 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?

For a zero-parameter, read-only tool with no output schema, the description fully conveys the data source, the metric (system load/demand), the real-time nature, and the geographic region. There is nothing missing that would prevent an agent from correctly invoking 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?

There are zero parameters, and the schema is empty, so parameter semantics are not applicable. Per the rubric, a baseline of 4 is given since no parameters exist to document; the description adds no parameter information because none is needed.

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 opens with a specific verb and resource: 'Get current ISO New England system load (demand)' and immediately distinguishes its real-time 5-minute nature. It also states the geographic scope (six states), clearly differentiating it from siblings like isone_fuel_mix.

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 clearly implies usage for current real-time load data but does not explicitly mention alternatives or when not to use it. The context is unambiguous—this is for ISO-NE demand—so an agent would not confuse it with other tools, but no exclusions are provided.

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