simulator_boot

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

With no annotations provided, the description carries the full burden. It only states the tool boots a device but doesn't disclose behavioral traits such as whether the device must already exist, if booting is synchronous or asynchronous, or what happens if the device is already booted (e.g., error vs no-op). No side effects or state changes are described.

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 a single, short sentence that is front-loaded and to the point. It uses minimal words to convey the core purpose. While it could be a bit more specific, it earns its place without unnecessary 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 low complexity (1 parameter, no nested objects, no output schema), the description is incomplete. It doesn't explain the boot process, prerequisites, or post-conditions. As a state-changing operation (booting a device), more context is needed for proper agent use.

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% with one parameter (deviceId) described as 'Simulator UDID or name'. The description adds no additional meaning beyond what the schema already provides. Since coverage is high, 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?

The description clearly states 'Boot a simulator device so it can be used', which identifies the action ('Boot') and the resource ('simulator device'). It distinguishes this tool from siblings like simulator_list, simulator_create, simulator_shutdown, etc. However, it doesn't specify what 'boot' means compared to 'open' (simulator_open), leaving a minor ambiguity.

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?

The description provides no guidance on when to use this tool versus alternatives. For instance, it doesn't explain when booting is needed instead of just opening the simulator (simulator_open), or whether booting is required before app_launch. No prerequisites or usage context are mentioned.

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