Get Home Info

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

With no annotations, the description provides the main behavioral signal: it lists all homes in the account and their properties, implying a read-only collection operation with no side effects. The response content is named even though the output schema exists.

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?

A single sentence that front-loads the resource ('Alle Homes im Tibber-Account') and then efficiently lists the returned fields. No filler 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?

The tool is simple, has zero parameters, and an output schema exists to specify the return structure. The description covers what the tool returns and its scope, which is sufficient for an agent to select and invoke it.

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 has no parameters, so parameter semantics are irrelevant. Per the rubric, zero parameters receive a baseline of 4; the description correctly does not invent parameter details.

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 identifies the exact resource ('Alle Homes im Tibber-Account') and the specific data returned: address, tariff status, meter point, and Pulse presence. This clearly distinguishes it from sibling price, forecast, consumption, and live-measurement tools.

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 makes clear it is for retrieving home/account metadata rather than pricing, consumption, or live measurement, so the use context is evident. It does not explicitly name alternatives or exclusion conditions, but none are needed for a zero-parameter metadata tool.

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