supervisor_get_host_info

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

No annotations are provided, so the description carries full burden. It discloses the nature of the tool (read-only info) and lists example data (HAOS version, hostname, kernel). However, it does not mention any prerequisites or permissions, though for a supervisor info tool these are implicitly understood.

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 concise sentence that front-loads the purpose and includes relevant examples. No unnecessary words or information.

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 with no parameters and an output schema exists. The description sufficiently explains the tool's purpose and sample outputs. All information needed to understand the tool's function is present.

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?

There are no parameters, and schema coverage is 100% trivially. Baseline for 0 parameters is 4. The description adds value by specifying what info is returned, which is not covered by the empty schema.

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 gets host OS info (HAOS version, hostname, kernel, etc.). It uses a specific verb ('Get') and resource ('host OS info'), and the name explicitly differentiates it from sibling supervisor tools like supervisor_get_core_info and supervisor_get_supervisor_info.

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 retrieving host OS information, but does not explicitly state when to prefer this tool over alternatives such as supervisor_get_core_info. No when-not or alternative guidance is provided.

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