Boot an iOS simulator

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

No annotations are provided, so the description carries the full burden. It mentions the underlying command (xcrun simctl boot), implying it launches a system process, and clarifies that it does not erase or reset content. However, it does not mention potential side effects like boot time or whether it waits for boot completion, which could be relevant for an agent.

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 with no fluff. The key action is front-loaded, and the usage guidance and exclusions are direct. Every sentence earns its place.

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 the simple tool (1 parameter, no output schema), the description covers purpose, usage, and a key exclusion. It could mention that booting may be asynchronous or require waiting, but for the tool's simplicity, this is nearly complete.

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?

The schema already describes the udid parameter with a helpful hint (use simulator_list first). Schema coverage is 100%, so the description doesn't need to add more. It adds no further semantics beyond the schema, so a baseline 3 is appropriate.

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 ('boot') and resource ('simulator by UDID'), with the exact command (xcrun simctl boot) and a clear scope: it does not erase or reset content. This clearly distinguishes it from sibling tools like simulator_shutdown and simulator_show.

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?

Explicitly states when to use this tool: before install_app, launch_app, screenshot, or open_deep_link, which are siblings. It also clarifies what it does not do (erase/reset), preventing misuse. This is excellent guidance.

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