IDM Solarstatus

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description goes further by enumerating the exact data fields returned (B73, B75, etc.), adding meaningful context about the tool's scope.

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 short and front-loaded, but there is minor redundancy between the German list of returned values and the English 'Returns' line that says 'JSON-Objekt mit Solardaten'. This slightly reduces conciseness but does not harm clarity.

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's zero parameters, strong read-only annotations, and existing output schema, the description adequately covers the data scope. It lists all major measurements and states the return format, making it complete for its simplicity.

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 tool has zero parameters, so there is no parameter detail to add. The schema is fully covered (100%) and the description correctly omits parameter information, matching the baseline for parameterless tools.

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 uses a specific verb ('Liest') and identifies the exact resource (Solarstatus der IDM Wärmepumpe), then lists the precise measurements returned. This clearly distinguishes it from sibling getter tools like idm_get_temperatures.

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 solar-specific data list implies when the tool is useful, but there is no explicit guidance on when to use it versus alternatives, nor any exclusions or comparisons with sibling tools.

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