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

With no annotations provided, the description carries the full behavioral disclosure burden. It explains the alert's screen-covering, tap-swallowing behavior, and that the tool returns a normal false result when no alert is present. It does not mention permission requirements or exact return fields, but the disclosed behavior is meaningful and accurate.

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 description is compact and front-loaded, leading with the core purpose. Every sentence adds value: the blocking behavior, the 'absence is normal' semantic, and the session requirement. The inline JSON example is a concise way to communicate expected false-case output.

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 simple single-parameter read tool, the description is mostly complete: it explains purpose, normal absence semantics, and prerequisite session. Since there is no output schema, it could have more explicitly detailed the true-case return shape, but the mention of 'text and button labels' gives sufficient guidance.

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%, and the udid parameter is already documented as 'iOS device UDID'. The description adds no additional parameter-level detail, so this matches the baseline for fully schema-covered parameters.

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 begins with a specific verb and resource: 'Check whether a system or app alert is currently blocking the iOS UI' and clarifies what it reads (text and button labels). It clearly separates this from the sibling ios_alert_respond by framing it as a status check rather than an action.

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?

It gives concrete context: 'worth checking before trusting a tap that "succeeded"' and notes that absence is a normal answer rather than an error. It also states the active iOS automation session requirement, but it does not explicitly contrast with ios_alert_respond or mention when not to use it.

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