powerwall_get_soe

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what is retrieved but does not mention whether authentication is required, whether any side effects exist, or how the value is returned. The 'Get' verb implies read-only, but this is not made explicit.

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?

A single, focused sentence with no filler. The lead 'Get state of energy' is immediately informative, and the parenthetical adds clarity about the unit of measurement.

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 and no annotations, the description only partially covers what the agent needs to know. It clarifies the output is a percentage but does not specify format/range or any dependency on a prior login. For a parameterless read, this is close, but still leaves minor uncertainty.

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 tool has zero parameters and the schema is complete (100% coverage of an empty object). The description does not need to add parameter details; the baseline for a parameterless tool is 4.

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 specific verb ('Get') and resource ('state of energy') and clarifies it as battery charge percentage, making the function's intent clear. However, it does not explicitly contrast with sibling getters such as powerwall_get_system_status, so it lacks an explicit sibling differentiation.

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 provides no guidance on when to prefer this tool over alternatives (e.g., powerwall_get_system_status, powerwall_get_meters_aggregates). It does not state prerequisites or use cases beyond the bare purpose, so an agent must infer usage entirely from the name.

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