set_max_parameter

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a mutating operation. The description adds the useful detail that the change happens 'on Growatt's side,' indicating an external state change, but it does not disclose side effects, permissions, or irreversibility beyond that. It is consistent with the annotations, not contradictory.

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 description is two short sentences with no filler. The primary purpose is front-loaded, and the second sentence adds relevant side-effect context rather than repeating schema information.

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 write operation, the description plus the fully documented schema and annotations is largely sufficient for an agent to invoke it correctly. The output schema exists, so return-value explanation is unnecessary. The main gap is the lack of routing guidance between set_max_parameter and set_device_parameter, but that is more a usage-guideline concern than an invocation-completeness gap.

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%, so all three parameters (device_sn, setting_type, values) are already documented with meaningful descriptions. The tool description itself adds no parameter-specific detail beyond the general 'setting' framing, which is fine given the schema already carries the semantic weight.

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 identifies a specific action, 'Write a setting,' and a specific resource, 'a MAX-series inverter.' It also adds that the operation changes state on Growatt's side, which helps an agent understand the real-world effect. It does not explicitly differentiate from sibling tools like set_device_parameter, so it stops short of a 5.

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 provides no guidance on when to use this tool versus alternatives such as set_device_parameter or read_device_parameter. The only implied context is the 'MAX-series inverter' qualifier, but there are no explicit conditions, exclusions, or recommended alternatives.

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