get_grid_status

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety and locality profile is covered. The description adds the scope of returned data (total plus per-phase, active and reactive, grid connection state), which is useful context, but it discloses nothing about freshness, caching, or error behavior beyond that.

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 telegraphic sentence with the resource front-loaded and zero filler. Every clause carries content and nothing is repeated from the schema or annotations.

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 an output schema documenting return values and annotations covering safety, the description is serviceable but thin: it offers no usage guidance or sibling routing, which is the one thing structured fields cannot supply. It is adequate rather than complete.

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 and schema coverage is 100%, so there is nothing for the description to compensate for; the baseline of 4 applies. No parameter syntax or defaults are needed for a no-argument read.

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 names a distinct resource (the grid connection point) and enumerates the data it exposes (total and per-phase active/reactive power, on/off-grid status), which is enough to separate it from get_plant_status, get_inverter_status, and get_battery_status by device scope. It stops short of a clear verb and never explicitly contrasts itself with those siblings, so it is clear but not maximally differentiated.

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?

There is no statement of when to call this versus the many sibling status tools (get_plant_status, get_energy_totals, get_inverter_status). An agent must infer that this is the tool for grid-connection data purely from the resource name in the sentence.

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