connect_inverter

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

No annotations are provided, so the description must cover behavioral aspects. It explains parameters (host, port, family, timeout, retries) and mentions port alternatives and family auto-detection. However, it does not describe connection persistence, lifecycle, or error behavior, which is a gap.

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 compact and front-loaded with a purpose statement, followed by a clear Arg list. Each sentence adds necessary information without redundancy, making it highly efficient.

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?

The description covers all parameters with detailed semantics, but lacks information on connection state management (e.g., disconnection, multiple connections). Given the output schema likely handles return values, the description is mostly complete but could include a note on reconnection behavior.

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?

With 0% schema description coverage, the description provides comprehensive parameter details: host example, port default and alternative usage, family list with auto-detection note, timeout unit, and retries count. This fully compensates for the schema's lack of descriptions.

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 'Connect to a GoodWe inverter over the local network,' specifying the resource and context. It distinguishes from sibling tools that focus on data retrieval or setting, making the purpose unambiguous.

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 as a prerequisite for other inverter tools but does not explicitly state when to use it or when not to. Including guidance such as 'Use this before reading sensor data' would enhance clarity.

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