adb_shell_close

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

Description states it closes the session and terminates the process, which is clear. No annotations exist, so description carries full burden. Could mention idempotency or handling of unread data, but overall sufficient.

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?

Single sentence with no wasted words. Efficiently conveys the tool's purpose and scope.

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 simple close tool with one parameter, the description is mostly complete. Could mention safety of calling multiple times, but not critical given the context.

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 has 100% coverage for the single parameter. Description does not add meaning beyond the schema's description of session_id. 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?

Description clearly states the action: 'Close an ADB shell session and terminate the adb process.' It uses a specific verb (close/terminate) and resource (ADB shell session), distinguishing it from siblings like adb_shell_open or adb_shell_exec.

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?

No explicit guidance on when to use vs. alternatives. It is implied that after opening a session (adb_shell_open) this should be called, but no mention of prerequisites, when not to use, or consequences of not calling.

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