Generator Start/Stop Control

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

The description claims the tool can 'control' (send manual start/stop command), contradicting the annotation readOnlyHint=true which indicates read-only behavior. No clarification is provided for this inconsistency, and no mention of destructive actions or side effects.

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 concise: two sentences. The first sentence lists capabilities, the second provides context (GX relay logic, unit ID). No superfluous content.

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 values are not needed. However, the description lacks guidance on when to use read vs. control operations, and the contradiction with annotations is unresolved. For a tool with both read and write capabilities, more context on control side effects is expected.

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?

All 7 parameters have descriptions in the input schema (100% coverage), so the description adds minimal parameter info beyond noting 'Unit ID is always 100'. The description does not elaborate on parameter usage or constraints beyond the 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 clearly states it retrieves GX generator auto start/stop status and provides control (manual start/stop command). It lists specific fields (SOC, load, voltage, etc.) and distinguishes from siblings like victron_genset_status by focusing on auto start/stop logic.

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 usage for status and control of generator start/stop, but does not explicitly state when to use this tool versus alternatives (e.g., victron_genset_status). No when-not or alternative guidance is provided.

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