Get latest readings

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

With no annotations provided, the description carries the behavioral disclosure burden. It adds useful interpretation beyond the schema by noting that generation is legitimately zero at night and that weather/irradiance are included where available. This helps the agent avoid misreading valid nighttime data as a failure.

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 short sentences, each earning its place: the first states the core behavior, the second gives the primary use case, and the third provides a critical interpretation caveat. It is front-loaded and free of filler.

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 simple read-style tool with two well-documented parameters and no output schema, the description is largely complete. It explains purpose, when to use it, and a key data-interpretation nuance. A small gap is that it does not describe what happens when no recent reading exists or how to interpret missing sources, but this is minor.

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?

Schema description coverage is 100%, so the schema already documents nodeId and sourceIds. The description reinforces the per-source aggregation concept and the optional restriction to specific source IDs, but does not need to add substantial parameter-level detail.

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 retrieves the most recent reading per source on a node, including weather and irradiance when available. This distinguishes it from siblings like query_datum or get_energy by focusing on latest status rather than history or aggregates.

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 explicitly tells the agent when to use it: for 'what is happening right now' and for checking if a stream is still live. It does not explicitly name alternatives or exclusion criteria, but the context is clear enough for correct selection.

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