set_inverter_mode

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

Since no annotations are provided, the description carries full disclosure burden. It identifies the operation as a write requiring confirmation, which is useful, but it does not explain what happens when confirmation is missing, whether the change is reversible, or any system impact. Behavior is only partially disclosed.

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?

Two short sentences with no filler. The mode list is directly useful, and the confirmation note is a necessary constraint. It is appropriately sized for the information it conveys.

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?

Although an output schema exists, the description lacks essential context: no usage guidance, no parameter semantics for instance/confirmed, and no behavioral consequences beyond confirmation. For a mutation tool with no annotations, this is insufficient for an agent to reliably invoke 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?

The input schema has 0% description coverage, so the description must explain all parameters. It lists the mode values but does not define them. The 'instance' parameter is entirely absent, and 'confirmed' is only implied by 'Requires confirmation,' not clearly mapped to the parameter. Significant semantic gaps remain.

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 clearly states the verb 'Set' and the resource 'inverter mode', and lists the accepted modes. This distinguishes it from sibling setters like set_charge_current_limit and set_soc_limit because the target parameter is explicitly named.

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?

No guidance is provided on when to use this tool versus alternatives. The only operational note, 'Requires confirmation for write operations', is a prerequisite rather than a usage condition, and it does not mention preconditions or alternative tools.

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