IDM Smart Grid Status setzen

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

Annotations already signal a write operation (readOnlyHint=false) and idempotency. The description adds the register address and the behavioral meaning of each mode (e.g., '0 = EVU-Sperre & kein PV-Ertrag'), providing context beyond the annotations without contradiction.

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 organized with a purpose sentence, a mode breakdown, and a future-use note, followed by Args/Returns. Every section is informative; no filler.

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?

With a single parameter, a detailed parameter explanation, a return type, and relevant usage context, the description is self-sufficient. The output schema further clarifies the response structure, and annotations cover the safety profile.

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 description includes an 'Args' section explaining params.status with the 0/1/2/4 semantics, complementing the schema's property description. This fully covers the parameter, even though the schema already documents it.

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 opens with a clear verb+resource statement ('Setzt den Smart Grid Status der IDM Wärmepumpe (Register 1006)') and expands on the meaning of each status value, distinguishing it from sibling setters like idm_set_system_mode or idm_set_pv_surplus.

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?

It identifies the use case (external control via energy market signals or E3DC/Victron) and even includes a future pricing-based usage hint, but it does not explicitly compare with alternative setters or state when not to use.

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