get_app_readiness

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the sample budget, the exact state vocabulary, which evidence sources are used per platform, explicitly unsupported capabilities (unresponsive detection, iOS signals that may be unknown), and that no automatic unlock or wake occurs. It also warns that settled UI is not proof of app identity or backend completion. It does not discuss cost, rate limits, or error behavior.

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 opening sentence is well front-loaded, but the body is a dense block of caveats of near-equal weight, mixing result structure, platform support, and epistemic disclaimers. Each sentence carries information, yet the absence of grouping or emphasis makes it harder to scan than it needs to be.

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?

Given no output schema and no annotations, the description does sketch the return shape (device_readiness with timestamped blocker evidence) and platform caveats, which is good. But the four input parameters remain entirely unexplained and no prerequisite or failure-mode guidance is given, so it is only partially complete for a tool of this complexity.

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 0% across four parameters, and the description compensates for none of them: deviceId, timeoutMs and stabilityMs have no explanation of semantics, defaults, or interaction (e.g., how stabilityMs relates to the two-sample budget). Only the platform enum is touched indirectly via 'Managed Android and supported iOS simulator'.

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 ('Observe readiness') plus the mechanism ('at most two fresh UI-tree samples') and the enumerated outcomes (loading, transitioning, settled, unknown). This differentiates it reasonably from the wait/expect siblings, though it never names them explicitly.

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 phrase 'at most two fresh UI-tree samples' implies a bounded, non-blocking observation in contrast to wait_for_app_ready, wait_for_ui and expect_state, so usage is implied. However, no explicit when-to-use statement or named alternative appears, leaving the agent to infer which readiness tool to pick.

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