adb_shell

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It notes the command is arbitrary, but does not disclose that the command may be destructive, whether raw output is returned, what happens on shell errors, or whether there are timeouts. The read-only example is not enough to convey the behavioral risk of arbitrary execution.

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, front-loaded sentence that states the action, its scope, and an illustrative example. Every element earns its place with no redundancy.

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 an arbitrary escape-hatch tool with no output schema or annotations, the description adequately covers purpose and selection but omits behavioral expectations such as return format and side-effect risk. This leaves an important gap for an agent deciding whether and how to invoke it.

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 the baseline is 3. The description's example illustrates the command format but adds little beyond the schema's 'Command line executed by the device shell' description, and it does not clarify serial semantics beyond what the schema already states.

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 tool runs arbitrary adb shell commands and explicitly frames it as a fallback for anything not covered by other tools. This distinguishes it from the many specialized sibling tools without requiring the agent to inspect each one.

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?

It gives explicit when-to-use guidance: use for anything not covered by the other tools. This also implies when-not-to-use, since any operation with a dedicated sibling tool should not go through this escape hatch.

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