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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, and the description adds real context beyond them: execution is sequential, non-blocking, and returns a run id immediately rather than results. It doesn't cover permissions, device-state side effects, or failure behavior, so it is strong but not exhaustive.

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 sentences, zero filler, front-loaded with the action and scope before the async return behavior and the follow-up polling call. Every clause carries information an agent needs.

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 an async fire-and-forget run tool with no output schema, the description supplies what the agent needs: what runs, how it runs, what is returned, and how to follow up. It omits auth requirements and behavior on partial failure, which would round it out.

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%, so the baseline is 3, but the description adds meaningful semantics for suiteId by explaining that the suite is resolved to include plans and one level of child suites, and ties udid to where the tests execute. The optional 'name' label is not mentioned, so it isn't a full 5.

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 ('Run every test in a suite') and precisely defines scope: the suite plus its plans plus one level of child suites, executed SEQUENTIALLY on a device. That scope detail distinguishes it from siblings like test_suite_run_status and flow_replay_start without needing to open either schema.

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?

Clearly frames the async workflow: the run happens in the background and the agent must poll test_suite_run_status(runId) for progress and the rollup report. It gives no explicit when-not or comparison to other run/execution siblings (e.g., flow_replay_start), so it stops short of full routing guidance.

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