set_device_power

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

Annotations already carry the destructive and non-read-only safety profile, so the description does not need to restate mutation. It adds 'Changes state on Growatt's side,' clarifying the change is server-side, but it does not describe reversibility, side effects, or failure behavior.

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 sentences with no filler. The core purpose is front-loaded, and the second sentence adds useful state-change context without unnecessary elaboration.

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 three-parameter mutation with full schema coverage and an output schema, the functional information needed to invoke the tool correctly is present. The only gap is explicit usage routing among sibling device commands, but the purpose line and annotations largely compensate.

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 100%, with detailed parameter descriptions including device-type-specific units for value and the source of device_type. The description itself adds no parameter-specific detail, so it stays at the baseline for a fully documented schema.

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 starts with a specific verb and object: 'Set the active power limit of a device.' This names the resource and the exact aspect being changed, which clearly distinguishes it from siblings like set_device_on_off and set_device_parameter.

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 implies when to use the tool through its purpose line, but it does not explicitly state alternatives or exclusions. An agent must infer that this is for power-limit changes rather than toggling power state or writing generic parameters.

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