alexa_list_smart_home

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description still adds real value by disclosing the scope of the entity inventory and which capabilities this server supports per device, information not present in the annotations. It stops short of describing pagination or response size behavior for large device fleets.

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?

Front-loaded with the core purpose and the alexa_list_devices exclusion, then the action-routing map, then the optional filter. The action mapping is dense but each clause earns its place by preventing a wrong sibling call. Slightly long, but no filler.

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?

With no output schema, the description carries the burden of explaining coverage and does so well, including the entity classes returned and the actions available per entity. Response shape is delegated to the view parameter in the schema, which is a reasonable division, though no return-shape detail is given beyond that.

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 description coverage is 100% – both parameters, including the compact/full view enum, are already documented in the schema. The description repeats the kind filter withexamples (THERMOSTAT, LIGHT, SMARTPLUG, SMARTLOCK, GARAGE_DOOR) but adds no syntax or semantics beyond what the schema already provides. Baseline 3 applies.

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?

States a specific verb (list) and a precisely scoped resource (smart-home devices, groups and scenes Alexa controls), enumerating entity types such as thermostats, locks, garage doors and scenes. It also explicitly contrasts itself with the similarly named sibling alexa_list_devices, so an agent can disambiguate without opening either schema.

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?

Provides an explicit when-not clause ("These are NOT in alexa_list_devices, which only lists Echo speakers...") and routes each entity type to the correct follow-up tool (setTemperature via alexa_set_thermostat, lock/unlock via alexa_lock, open/close via alexa_garage_door, modes via alexa_set_device_mode, the rest via alexa_control_smart_home). This is a full decision map, not implied guidance.

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