Boot iOS Simulator [Pro]

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

No annotations are provided, so the description carries full burden. It indicates this is a boot (startup) operation and notes it's a Pro feature, but doesn't mention side effects (e.g., if the simulator is already booted) or permissions needed. Adequate but minimal.

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?

Two short, front-loaded sentences. Every sentence serves a purpose: one states the action and requirement, the other provides the source for the required data. No fluff.

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 tool is simple (one required parameter, no output schema, no nested objects), the description is complete. It tells what to do and where to get the identifier. Could mention if it fails silently or requires a simulator to be created first, but for a straightforward boot operation it's sufficient.

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% (one parameter 'device_id' described as 'Simulator UDID'). The description adds context that the UDID comes from ios_list_simulators, which links to a sibling tool, but doesn't add meaning beyond what the schema provides. Baseline 3 stands.

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?

Clearly states the specific action (boot an iOS simulator) and the required resource (by UDID). Distinguishes itself from sibling tools like ios_shutdown_simulator by the action and uses '[Pro]' to indicate a pro feature.

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 instructs to get the UDID from another tool (ios_list_simulators), providing a clear prerequisite. No explicit when-not-to-use guidance, but it's implied to be used after listing simulators.

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