List Omada devices

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds nothing beyond that – no pagination behavior, no filtering behavior, no statement about what happens when the site has no devices or how unauthorized sites are handled.

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?

A single front-loaded sentence is appropriately sized, but it trails off with an ellipsis ('uptime…'), which reads as an unfinished field list rather than a deliberate summary. Tightening the truncation would cost nothing.

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?

A read-only, one-parameter listing tool with a rich annotation set and an output schema is a low-burden case, so the description is close to adequate. The remaining gap is the unexplained 'site' parameter, which neither the schema nor the description clarifies.

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 sole parameter 'site' has 0% schema description coverage, so the description must carry its meaning, but it only says 'on the site' without stating the expected identifier format or what happens when it is omitted. With one undocumented optional parameter, this leaves the agent guessing.

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 and resource: 'List all managed network devices' and names the concrete device types (APs, switches, gateways) with the site scope. This distinguishes it from client-oriented siblings such as list_clients, but it never contrasts itself with get_device for single-device retrieval.

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?

There is no explicit when-to-use guidance, no mention of when not to use it, and no pointer to alternatives like get_device or list_clients. Usage is only inferable from the verb 'List' and the site phrasing.

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