List Devices

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

No annotations are provided, so the description must fully disclose behavior. It explains the output includes channels, types, and addresses, and describes optional filters, but does not mention pagination, ordering, or performance characteristics. The description is adequate but not rich.

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?

Two sentences: first states purpose and output, second provides filter summary and usage guidance. Every word is earned; no fluff 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?

For a list tool with no output schema, the description adequately describes the return items (devices with channels, types, addresses). It also integrates with sibling context by advising usage before get_value/set_value. Could mention pagination but overall complete for typical use.

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 100% coverage with each parameter documented. The description redundantly lists the optional filters but adds a helpful example for the 'type' parameter (e.g., 'HmIP-eTRV-2'). This adds minimal value beyond the 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 it lists devices with their channels, types, and addresses. It includes a specific verb ('List') and resource ('devices'), and distinguishes itself from siblings by advising to use it first for get_value/set_value.

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 explicitly says 'Use this first to discover device addresses for get_value/set_value,' providing clear context for when to use the tool. However, it does not mention when not to use it or alternative tools for device discovery.

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