configure_inverter

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

With no annotations, the description carries full burden and delivers: it discloses saving to ~/.fronius-mcp.json with persistence, automatic scheme/port stripping, and return behavior (confirmation or connectivity warning).

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?

Description is concise (4 sentences plus Args/Returns) and well-structured with clear sections. Every sentence adds value; minor redundancy ('useful for first-time setup' is implicit) but overall 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?

Given the tool's simplicity (1 param, no nesting), the description covers purpose, usage, side effects, parameter details, and return behavior. Output schema exists and description explains return values adequately. Sibling tools are distinct.

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 provides only 'Host' string without description (0% coverage). The description compensates fully: specifies IP/hostname format, example, and behavior (scheme/port stripping).

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 'Configure the Fronius inverter IP address or hostname.' It specifies the verb (configure) and resource (inverter IP/hostname), and distinguishes itself from sibling tools (solar_battery, solar_devices, etc.) which handle other aspects.

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 says 'Call this once to tell the MCP server where your inverter lives' and notes persistence across restarts. It implies a one-time setup but could explicitly state when not to use or that it's a prerequisite for other tools. Still clear overall.

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