get_storage_realtime

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions real-time nature and data fields but does not describe error behavior, authentication requirements, or the effect of optional deviceId on output. For a simple read tool, this is minimal but lacks depth.

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 concise sentence that directly states the tool's purpose and key output data. It is well-structured and free of unnecessary words, every word contributing to the meaning.

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 has only one optional parameter and no output schema or annotations, the description provides adequate basic context. However, it does not explain the response format or handle edge cases like invalid deviceId, making it somewhat incomplete but acceptable for a straightforward getter.

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 covers the single parameter deviceId with a clear description and default behavior, giving 100% schema coverage. The tool description adds no additional parameter semantics beyond what the schema already states, so the baseline score of 3 applies.

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 gets real-time battery storage data and lists the specific metrics (state of charge, power, temperature). This distinguishes it from sibling real-time tools like get_inverter_realtime or get_meter_realtime, which target different resources.

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 clear context that this tool is for storage-specific real-time data, implying when to use it. However, it does not explicitly mention alternatives or exclusions, but the resource naming is sufficient to differentiate it from other real-time data tools.

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