iOS Simulator: Erase

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description goes further by naming precisely what is destroyed (apps, data, keychain, permissions), that it is irreversible, and a non-obvious side effect: a booted simulator is shut down then re-booted because simctl refuses to erase a running one. That is real behavioral context beyond the annotations.

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 destructive scope before the alternative and the mechanical side effect. 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 a destructive, two-parameter tool with no output schema, the definition is complete: safety profile (via annotations plus the description), scope of destruction, reversibility, sibling routing, and the shutdown/reboot side effect are all covered.

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; the description earns an upgrade by explaining the rationale for `confirm` ('Irreversible, hence confirm') rather than just restating it. It does not add anything about `device` beyond the schema, which already documents UDID/name omission and the never-picks-arbitrarily guarantee.

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 ('Wipe... back to a factory state') and enumerates exactly what is destroyed: installed apps, their data, the keychain and every granted permission. It explicitly separates itself from ios_simulator_uninstall, so an agent can route correctly without opening 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?

Names the sibling alternative and the condition that selects it: use uninstall when the goal is merely 'a first launch of one app' rather than a full reset. The irreversibility note plus the required `confirm` also tells the agent this is a last-resort operation.

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