solaredge_live_status

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

The description provides detailed behavioral context, clarifying that energy_today_wh is AC production and pv_generation_today_wh includes DC-coupled battery energy. With no annotations, this fully informs the agent.

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?

Three sentences, no fluff. The first sentence provides an overview, the second clarifies a technical distinction. Every sentence adds value.

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 presence of an output schema and no parameters, the description covers all necessary context: what data is returned and how to interpret key metrics.

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?

There are no parameters, so schema coverage is 100%. The description appropriately adds no parameter information, meeting the baseline for a zero-parameter tool.

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 tool returns current power, energy flow, battery charge, and production metrics. It distinguishes itself from siblings like diagnosis and analysis by focusing on live instantaneous status.

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 use for live monitoring, but does not explicitly state when to use vs. alternatives. However, the context and sibling names make it clear enough.

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