List smart-home devices (with source)

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

With no annotations, the description carries the burden. It details the output fields and their interpretation (prefix meanings), which is helpful. However, it does not mention that the tool is read-only, whether authentication is needed, or any constraints like pagination. Safety information is missing.

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 consists of two sentences, with the first sentence immediately stating what the tool returns. Every word adds value, and the structure is efficient. No redundancy or unnecessary details.

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?

While the output fields are well described, the parameters are completely ignored, making the tool definition incomplete. Given no output schema, the description compensates partially but fails to address the input schema gap. The use case is clear, but parameter semantics are missing.

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 schema has 2 parameters (manufacturer, onlyManufacturer) with 0% description coverage. The tool description does not explain their purpose or how they affect results. For a tool with parameters, the description should clarify their semantics, but it remains silent.

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 returns all smart-home devices with specific fields (applianceId, source, backing entity id). It distinguishes from siblings like 'alexa_list_devices' by focusing on smart-home devices and mentioning a specific use case (finding orphaned devices). The verb 'list' is implied, and the title reinforces the purpose.

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 to use this for finding orphaned devices, providing a clear context. However, it does not explicitly contrast with alternatives or mention when not to use it. The sibling tools are not referenced, so guidance is somewhat implicit.

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