ios_close_session

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

Annotations already indicate a mutating, externally visible, idempotent operation that is not destructive. The description adds useful context about what gets affected (device and WebDriverAgent runner), but does not go beyond that to describe edge behaviors such as effects on running apps or session cleanup details.

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?

A single, direct sentence that front-loads the action and target. Every word earns its place, with no filler or redundant restatement of the tool name.

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?

For a zero-parameter, low-complexity tool with output schema and annotations available, this description fully conveys what the operation does. An agent can correctly select and invoke the tool based on this definition.

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 tool has zero parameters and the schema documents this fully with 100% coverage. The baseline for a zero-parameter tool is 4, and the description adds no contradictory or missing parameter semantics.

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 uses specific verbs ('release', 'shut down') tied to a clear resource (the device and its WebDriverAgent runner). It directly identifies the tool as the closing counterpart to ios_open_session and is distinguishable from siblings like ios_halt and ios_resume.

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 the tool is used when a session should be ended and the device released, but it does not explicitly state when to use it versus alternatives like ios_halt or ios_open_session. The usage context is inferable but not stated outright.

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