List Hubitat devices

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the Rule Machine exclusion detail, which is useful behavioral context not in annotations. It could add pagination/return-volume behavior, but the output schema covers return format. Annotations carry most of the burden, so a 3 is fair.

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?

Four short, purposeful sentences with zero filler. Every sentence earns its place: return fields, when to use, when not to use, and an explicit exclusion caveat. Front-loaded with the purpose statement before usage guidance.

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?

Output schema exists and covers the return shape. The description appropriately handles usage context, scope limitations (Maker API only, no Rule Machine), and sibling differentiation. Could add a note about default limit or result ordering, but for a list/discovery tool with good annotations and full schema coverage, this is essentially 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?

Schema description coverage is 100%, so all three parameters (limit, query, offset) are fully documented in the schema. The description doesn't add parameter-level detail but doesn't need to. Baseline 3 is correct when schema already documents parameters completely.

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?

Clear verb+resource ('List devices authorized in Maker API') plus explicit return fields (id, name, label, room, capabilities summary). Distinguishes from siblings by noting it lists only Maker API-visible devices, separate from hubitat_list_virtual_devices and hubitat_get_device. The scope constraint (only what Maker API sees) is specific and helpful.

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?

Explicit 'Use when' (discovering devices or finding an ID before send_command) and 'Do NOT use when' (already know the ID, use hubitat_get_device) with a named alternative. Also explicitly excludes Rule Machine rules, clarifying what is NOT returned. This is exemplary when/when-not framing.

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