adb_pull

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It doesn't mention whether the local path will be created/overwritten, what happens if the remote file doesn't exist, whether permissions are needed, or what the tool returns on success/failure. For a file operation tool with zero annotation coverage, this is a minimal disclosure.

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, zero wasted words. The description is appropriately terse for a simple file transfer operation, though it could be slightly more informative without losing conciseness.

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?

This is a mechanically straightforward file copy tool with no output schema and only 2 required params. The description covers the core operation adequately. However, given the complete lack of annotations and no behavioral details, the description is at minimum completeness for a simple tool but doesn't address failure modes, path validation, or overwrite behavior.

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 only 33% - only the 'serial' parameter has a description. The description adds that 'remote' refers to the file on the device and 'local' is the local destination, but only implicitly through the tool description. It doesn't specify path formats (absolute vs relative, remote path constraints) beyond what the schema provides. The description partially compensates for the low coverage by clarifying the direction of transfer.

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 (copy a file) and direction (device to local), distinguishing it from its sibling adb_push which copies in the opposite direction. Verb+resource+direction are all specified, making the purpose unambiguous.

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. The direction is implied by the name (pull = device to local) and the description, but there's no context about prerequisites (device connected, file existence) or when adb_push would be appropriate instead.

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