Enhanced ADB MCP Server

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a write operation ('push') but doesn't disclose critical details like whether it overwrites existing files, requires specific permissions, handles errors, or has side effects (e.g., affecting device storage). This leaves significant gaps for an agent to understand the tool's behavior safely.

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 extremely concise—a single, direct sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by conveying the essential purpose without 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?

Given the complexity (a file transfer operation with 3 parameters), lack of annotations, and 0% schema coverage, the description is incomplete. While an output schema exists (which might cover return values), the description fails to address key contextual aspects like error conditions, device state requirements, or interaction with sibling tools (e.g., 'pull_file'), leaving the agent with insufficient guidance for reliable use.

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 0%, so the description must compensate but adds no parameter information. It doesn't explain what 'local_path', 'remote_path', or 'device_serial' mean, their formats, or examples (e.g., absolute vs. relative paths). This leaves all three parameters semantically unclear beyond their titles in the 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?

The description clearly states the action ('push') and resource ('a file to the device'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'pull_file' by specifying directionality, though it doesn't explicitly differentiate from other file-related tools like 'list_files' or 'read_file' beyond the core action.

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 guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., device connectivity), constraints (e.g., file size limits), or when to choose other tools like 'install_apk' for APK files or 'shell_command' for advanced transfers. The description only states what it does, not when it's appropriate.

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