get_inverter_realtime

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

No annotations are provided, so the description must convey behavioral traits. It only states 'Get real-time inverter data', implying a read operation but giving no details on caching, rate limits, authentication, or data freshness. The behavioral transparency is minimal beyond what 'get' implies.

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 sentence of 9 words, front-loaded with the action and resource. Every word contributes to the core message. There is no fluff or repetition.

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?

For a read-only tool with two optional params and no output schema, the description covers the core output fields. However, it doesn't explain the impact of the dataCollection parameter on returned fields, nor any usage context. It is minimally adequate but leaves gaps in how to choose dataCollection or interpret results.

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 already provides 100% coverage for both parameters (deviceId and dataCollection) with descriptions. The description adds no additional parameter semantics; it only lists output fields (power, energy, voltage, current). Baseline 3 is appropriate since the schema handles parameter documentation fully.

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's purpose: 'Get real-time inverter data' with specific data types (power, energy, voltage, current). This distinguishes it from siblings like get_inverter_info (static info) and get_meter_realtime (meter data), though it doesn't explicitly name alternatives.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of scenarios, prerequisites, or exclusions. The description is a single statement without contextual usage advice, making it insufficient for an agent deciding between this and sibling tools.

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