shutdown

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

With no annotations, the description must disclose behavior itself. It adds a useful operational detail (90s timeout) and the verb clearly indicates a power-off action, but it omits other behavioral context such as whether the shutdown is graceful, whether a running target is required, or what side effects occur on the device/session.

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 sentences with no filler: the action is front-loaded and the timeout constraint is a separate, relevant operational note. Every word 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?

The presence of an output schema and full parameter descriptions reduce the need to explain return values or individual fields. Still, for a tool with 15 optional parameters and no required fields, the description leaves target selection ambiguous ('selected' is not mapped to the selectors).

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%, so all 15 parameters already have individual descriptions. The tool description adds no guidance about which selector fields (udid, serial, device, platform, session, etc.) are alternatives or how to construct a valid target, so it does not improve on the schema here.

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 states a specific verb and resource ('Shutdown a selected simulator or emulator'), so the core function is clear. However, it does not explicitly distinguish itself from sibling tools like boot or close; it relies on the tool name to carry that differentiation.

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 use case is implied: call this when a selected simulator or emulator needs to be powered off. It offers no explicit guidance about when not to use it, how it relates to boot/close, or which of the many optional selector parameters should be supplied.

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