list_devices

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

The description complements annotations by explaining the output fields, filtering support, and the fact that it lists all adopted devices. Annotations already denote read-only and idempotent behavior, so the description adds meaningful context without contradiction.

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?

Three concise sentences, front-loaded with core functionality. Every sentence adds value with no wasted words.

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?

Covers purpose, use cases, output fields, filter examples, and role determination. Given the simple parameters and no output schema, the description is complete and sufficient for effective tool selection.

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 coverage is 100% with good param descriptions. The description adds a concrete filter example but doesn't significantly augment the schema. Baseline 3 is appropriate.

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 adopted UniFi devices with specific fields (state, firmware, model, IP, MAC) and enumerates device types. It doesn't explicitly distinguish from sibling tools like list_clients, but the resource focus is 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?

Explicit use cases are provided (assess fleet health, find OFFLINE devices, check firmware updates) along with guidance on determining device roles from features. Lacks explicit when-not-to-use instructions, but the context is sufficient.

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