as_adb_shell

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

Adds significant detail beyond annotations (destructiveHint=true): explains confirm mechanism, safe/destructive command patterns, and return format (JSON with stdout/stderr or confirmation_required). No contradiction.

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?

Reasonably concise with a clear opening sentence. Two short paragraphs cover purpose, safety, and returns. Could be slightly tighter but well-structured.

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?

Given tool complexity (arbitrary shell commands), the description covers behavior, safety, parameters, and return value. With annotations and output schema assumed, it is complete and self-contained.

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 covers all params with descriptions (so coverage is high). Description adds value by explaining the safety logic behind the confirm parameter and listing example words. Adds context beyond schema.

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?

Clearly states 'Run a shell command on the device' as verb+resource. Distinguishes from sibling adb-specific tools by being generic, and details safe vs destructive commands.

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?

Explicitly explains when confirm=true is needed, lists safe first-words and dangerous markers. Lacks explicit 'when not to use' but context implies use for arbitrary shell commands, not specific adb operations.

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