opendss_run_command

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the mutation profile is covered structurally. The description adds the useful 'after compilation' timing constraint but says nothing about what happens on an invalid command, error handling, or the scope of arbitrary text execution, so it does not go far beyond the annotations.

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-loads the operation in the first sentence, then uses clearly delimited Args/Returns blocks. No filler, though the 'or confirmation of execution' hedging on returns is slightly soft.

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?

An output schema exists, so return-value explanation is optional and the description covers it anyway. For a tool that executes arbitrary DSS text, the description omits any caution about command validity or failure modes, leaving it only minimally adequate given the annotations.

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?

One parameter with 0% schema description coverage, and the description only offers 'RunCommandInput with the DSS command string' – effectively restating the parameter. There is no example command syntax, format, or delimiter guidance to compensate for the coverage gap on an arbitrary-string input.

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: 'Execute a single OpenDSS text command on the currently loaded circuit.' An agent can distinguish it from bulk compilation siblings, but it never explicitly contrasts itself with the structured edit siblings (opendss_edit_element, opendss_add_element) that overlap in purpose.

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 implied usage context ('useful for modifying the circuit after compilation'), which orients the agent toward post-compile mutation. However, it names no alternative and gives no when-not-to-use guidance, which is a real gap given three siblings that also add/modify circuit elements.

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