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

Annotations already declare non-readOnly, non-idempotent, non-destructive. The description adds real behavioral context beyond them: that accept/dismiss press the alert's DEFAULT controls (a semantic that determines correctness), and that an active iOS automation session is required. It does not cover failure modes when no alert is present, but the additions are substantive.

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?

Front-loads the core action in the first clause, then layers routing and parameter guidance. Slightly dense with em-dashes and a long example list, but each sentence carries distinct information; 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?

For a mutation tool with no output schema and 4 params, it covers purpose, alternative tool, button-selection logic, text-input ordering, and the session prerequisite. The only gap is behavior when no alert is on screen, which is minor given the otherwise complete picture.

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 baseline is 3, but the description goes beyond the schema by explaining the interaction semantics: 'accept'/'dismiss' map to default controls, `button` overrides by label, and `text` is typed into the first text field BEFORE the button press. That ordering and precedence is not derivable from the schema alone.

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 (answer) and resource (the alert currently on screen) and enumerates the three modes: accept, dismiss, or press a labeled button. It is cleanly distinguished from its sibling ios_alert_status, which it explicitly casts as the read step rather than the 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?

Gives explicit routing: call ios_alert_status first, then explains exactly when 'accept'/'dismiss' are wrong (non-standard button triples like 'Allow Once' / 'While Using the App' / 'Don't Allow') and that `button` is the correct path for those. This is a when-to-use/when-not-to-use statement with a named alternative.

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