ios_halt

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

Annotations already convey idempotent=true, readOnly=false, and destructive=false, lowering the burden on the description. The description adds some behavioral context by saying the session stops taking further action, but it does not disclose whether the session can be resumed, what happens to pending tasks, or any side effects. No contradiction with annotations was found.

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 with no filler. It is front-loaded and every word carries meaning, especially the phrase 'from taking further action', which distinguishes halting from closing or resuming.

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 tool this simple, the description is mostly sufficient, especially with annotations and an output schema present. However, it leaves out whether the action is reversible and how it relates to ios_resume or ios_close_session, which are important contextual cues for an agent choosing between sibling tools.

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 schema covers both the reason parameter and its default value with 100% coverage, so the description does not need to add parameter detail. The description adds no additional meaning about the 'reason' field, but the baseline of 3 is appropriate because the schema already documents it fully.

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 a specific verb ('Stop') and resource ('this session') and states the effect ('from taking further action'). It is clear about what the tool does, though it does not explicitly contrast itself with sibling tools like ios_close_session or ios_resume, so it is not fully self-differentiating.

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 gives no guidance on when to use this tool versus alternatives such as ios_close_session or ios_resume. There is no mention of situations where one should close the session instead of halting it, nor whether this action is pause-like or final.

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