get_live_measurement

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

With no annotations provided, the description carries full burden. It discloses a 15-second timeout and requirement for a Tibber Pulse at the meter. However, it does not specify behavior if the Pulse is unavailable or error handling, but the main behavioral aspects are covered.

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 relatively concise and front-loaded with key information. The first sentence covers purpose and output, followed by timeout and requirement. While slightly verbose in the first sentence, it contains no unnecessary words.

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?

The description covers output, timeout, and prerequisite adequately for a simple tool with an output schema. However, it omits explanation of the optional home_id parameter and how it affects results, leaving ambiguity for multi-home users. The output schema compensates for return values, but parameter context is incomplete.

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 single parameter home_id is optional and has no description in the schema (0% coverage). The description does not explain its purpose, format, or how it affects the tool's behavior. Given the lack of schema descriptions, the description should compensate but fails to add meaningful parameter context.

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 it provides live measurements from Tibber Pulse: current power, min/max, daily consumption and costs. It distinguishes itself from siblings like get_consumption (historical) and get_home_info (general info) by focusing on real-time data with a timeout.

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 usage when real-time data is needed from a Tibber Pulse device, but does not explicitly state when to use vs alternatives or provide exclusions. No guidance on when not to use or prerequisites beyond needing a Pulse.

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