list_devices

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

With no annotations, the description carries the full burden of behavior and covers it well: it discloses that all pages are drained by default, that page_token switches to single-page mode with a nextToken cursor, and that a capped drain returns incomplete=true instead of truncating silently. These are genuinely valuable behavioral details beyond what a basic list description provides.

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 purpose is front-loaded in the first sentence, followed by a concise parameter note and a tight explanation of paging behavior. Every sentence adds information needed to call the tool correctly, with 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?

The description covers the tool's purpose, both optional parameters, accepted host formats, and the non-obvious pagination/truncation contract. Since an output schema exists to document return values, nothing essential is missing for an agent to invoke this correctly.

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?

Despite 0% schema description coverage, the description documents both parameters: host accepts a console name, ID, or composite MAC:numericId format, and page_token controls manual single-page fetching with a nextToken cursor. This fully compensates for the bare input schema.

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 opens with a specific verb and resource: 'List all devices across the fleet with status, firmware, and model,' which makes the core purpose immediately clear. It does not explicitly differentiate this tool from the sibling list_all_devices or list_site_devices, so it misses the top score.

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 gives clear context for when to use the tool: to get a fleet-wide device listing, optionally filtered by host, and it explains the default full-drain behavior versus manual page_token fetching. It does not explicitly name when-not-to-use alternatives, but the usage context is clear and not merely implied.

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