unifi_devices

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

The description goes beyond annotations by classifying each operation as Read, Create, Destructive, or Admin, and clearly flagging any destructive or admin actions as requiring confirm:true. It also details pagination behavior and filtering semantics, giving a fuller picture of the tool's effects.

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 long but well-structured with a clear operations list and grouped information for pagination, filtering, and request bodies. Every section serves a purpose, though some details (e.g., filter grammar) could arguably live in a sub-spec without loss.

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?

The description covers list/filter/pagination well and references unifi_spec for request bodies, but it leaves some operation behaviors underspecified (e.g., execute_action vs execute_port_action) and does not describe return shapes for non-list operations. A complex multi-operation tool would benefit from a bit more detail or a pointer to output specs.

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%, providing baseline value. The description adds meaning by explaining the filter expression grammar (eq, like, contains, etc.), pagination structure, and confirm semantics, complementing the schema's per-parameter notes.

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 this tool manages UniFi devices, listing eight concrete operations (adopt, remove, get, statistics, etc.) with a title summarizing the scope. This distinguishes it from sibling tools like unifi_clients or unifi_sites.

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 clear context on when to use this tool (device operations) and explicitly directs users to unifi_spec for request-body shapes, which is helpful complementary guidance. It lacks explicit when-not-to-use alternatives, but the resource focus is unambiguous.

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