opendss_voltage_summary

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: the exact statistic set and the concrete violation thresholds (below 0.95 pu, above 1.05 pu) that define what 'violation counts' means.

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 core purpose is front-loaded in the first sentence, with the threshold detail immediately after. The trailing 'Returns: Voltage statistics summary' is redundant given the enumerated stats and the existing output schema, a minor waste.

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 read-only summary tool with an output schema and full annotation coverage, the description supplies the statistic set and threshold definitions an agent needs. The only meaningful gap is its relationship to the overlapping violation/voltage siblings.

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 reported at 0%, so the description should compensate; it only names the kv_min/kv_max filters without explaining their semantics (the actual kV-base meaning lives in the nested schema descriptions). This is a minimum-viable baseline rather than real added meaning.

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 verb and resource ('Get voltage statistics') and enumerates exactly what is returned (min, max, mean, std, violation counts). It is distinguishable from most siblings, though it does not explicitly separate itself from the overlapping opendss_violations or opendss_get_voltages tools.

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 a quick overview of the voltage regulation status' implies the high-level use case, but no explicit when-to-use or when-not-to-use guidance is given, and the related sibling opendss_violations is never mentioned as an alternative. Usage is left to inference.

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