iot_list_devices

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

With no annotations provided, the description carries the burden of behavioral disclosure. It only states it lists and filters devices, but does not mention pagination, maximum results, authentication requirements, or whether the list is real-time or cached. As a read-only operation, more context would be helpful.

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 two compact sentences, front-loaded with the action and resource, and mentions all filter capabilities without unnecessary verbosity. Every word earns its place.

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 simple list tool with three optional filters and no output schema, the description covers the core behavior: listing all devices and filtering. It lacks detail on return format or default behavior, but the simplicity of the tool reduces the need for extensive context. It is mostly complete.

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 provides 100% coverage with descriptions for each parameter (tag, type, filter). The description merely restates these filter options without adding extra examples, constraints, or interaction details. Baseline of 3 is appropriate because the schema does the heavy lifting.

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 lists all devices in the inventory and specifies filtering options (type, tag, search text). This distinguishes it from vendor-specific list tools like sonoff_list_devices or tb_list_devices, making the purpose specific and unambiguous.

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 provides no guidance on when to use this tool versus alternatives such as sonoff_list_devices or tb_list_devices. It doesn't mention whether this tool covers all IoT device types or if specific vendor tools should be preferred for vendor-specific queries.

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