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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower; the description still adds useful behavior: a default of 50 per page and the fact that the response text reports the total match count. It doesn't mention rate limits or ordering of results, which would be the remaining useful detail.

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 short sentences, purpose first, then filters/paging, then the return-count note. No padding, though the mid-sentence list of filter axes largely duplicates what the schema lists explicitly.

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?

For a read-only, no-required-parameter list tool with full schema coverage and no output schema, the description covers purpose, filtering, pagination defaults, and one return-value fact (total matched). Only the absence of guidance about empty results or result ordering keeps it short of 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%, with enums and bounds already declared, so the schema carries the parameter meaning. The description only restates the filter axes and repeats the 50-per-page default; it adds no syntax or matching detail beyond the schema (e.g. that deviceName is a case-insensitive substring match is only in the 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?

States a specific verb and resource: lists real devices available on TestMu AI for mobile app testing, with the scoping dimension (real devices, mobile apps) that separates it from platform-listing siblings. It doesn't explicitly name a sibling such as getSupportedPlatforms or uploadAppVirtualDevice, so the real-vs-virtual distinction is only implied.

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 tells you what you can filter by, which implies the intended use (find a device matching criteria), but never states when to call this instead of getSupportedPlatforms or before uploadAppVirtualDevice. No exclusions or prerequisites are given.

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