Shutdown iOS Simulator [Pro]

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 states that the simulator must be 'running' (a constraint), but does not disclose whether the operation is safe or destructive, or any side effects (e.g., unsaved data loss). The description adds minimal behavioral context beyond the action itself.

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 sentence of 9 words, conveying essential information without extraneous text. It is front-loaded with the action and resource, and efficiently uses parentheses for the UDID specification.

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?

The tool is simple with one required parameter and no output schema, so the description is mostly complete. However, it lacks mention of error cases (e.g., simulator not found) or behavioral details like safe shutdown vs force kill. Given the simplicity, a 3 is appropriate.

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% with one parameter 'device_id' described as 'Simulator UDID'. The description names the parameter ('by its UDID') and its purpose, aligning with the schema. It provides enough context for selecting the correct parameter value.

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 the action ('Shutdown'), the resource ('running iOS simulator'), and the identifier ('by its UDID'). It distinguishes the tool from siblings like ios_boot_simulator and ios_list_simulators, though it could be more specific.

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 implies use when a simulator is running and needs to be shut down, but provides no guidance on when not to use it (e.g., if simulator is already off) or alternatives. Since there is a sibling ios_boot_simulator, the description could clarify that this tool is for shutdown only.

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