vaillant_get_status

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

With no annotations provided, the description carries the full burden. It explicitly states 'Read-only,' indicating no side effects, and lists the specific data fields returned. This provides clear behavioral context for a read operation.

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 sentence that is front-loaded with the key purpose ('Current snapshot') and lists the data types. Every word adds value; no redundancy or waste.

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 simplicity of the tool (one optional parameter, read-only, no output schema), the description adequately covers the return values (list of data points). It does not specify the exact format (e.g., JSON object), but for a status snapshot this is acceptable.

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 coverage is 100% (the parameter 'system_id' is documented in the input schema). The description does not add any meaning beyond the schema; it does not mention the parameter or its default behavior. Baseline score of 3 is appropriate.

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 a 'current snapshot' of the Vaillant heat pump system, listing specific data points (outdoor temperature, water pressure, etc.). This distinguishes it from sibling tools like vaillant_get_devices or vaillant_get_diagnostics, which have different purposes.

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 for a system status snapshot and labels it 'Read-only,' but does not explicitly state when to use it versus alternatives or provide exclusion criteria. The sibling tools are mentioned in context but not differentiated in usage.

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