powerwall_get_networks

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

No annotations are present, so the description carries the full behavioral burden. The phrase 'WiFi network information' is generic and does not specify whether this returns nearby/available networks, the current connection, or network configuration, nor any prerequisites. The read-oriented verb is the only behavioral information.

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 a single six-word verb phrase with no filler, front-loading the operation and resource. It is appropriately concise for this simple tool, though that brevity comes at the expense of behavioral detail.

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 no output schema, the description does not explain what 'WiFi network information' concretely contains, leaving an agent to guess the return shape. However, the call requires no inputs and the operation is simple, so the gap is moderate rather than severe.

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 input schema has zero parameters and 100% schema description coverage, so there is nothing for the description to add. A baseline of 4 is appropriate for a parameterless call.

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 uses a clear verb ('Get') and a specific resource ('WiFi network information'), which is distinct from sibling getters like system status or site info. It doesn't explicitly contrast with siblings, but the resource name leaves little ambiguity about what is returned.

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?

No when-to-use guidance or alternative routing is provided. With 17 sibling tools all following the same 'get_*' pattern, an agent must rely on naming conventions alone to choose this tool. There are no conditions, prerequisites, or exclusions stated.

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