adb_file_write

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

Discloses that content is delivered via shell heredoc, has a size limit of ~128KB, and supports appending. With no annotations provided, the description carries full burden and does so effectively, providing key behavioral context.

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 concise with 4 sentences, front-loaded with the primary action, and efficiently covers purpose, mechanism, limits, and alternative. No extraneous information.

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 5 parameters, 100% schema coverage, no output schema, and no annotations, the description provides essential context (limits, suitable uses, alternative). It is fairly complete, though it could mention success/failure behavior or directory creation.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the shell heredoc mechanism and the 128KB limit, which provides context beyond the schema's parameter descriptions.

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's purpose: 'Create or overwrite a text file on the device.' It specifies the mechanism (shell heredoc) and distinguishes from sibling tool adb_push for large or binary files.

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 advises to use adb_push for large or binary files and notes shell buffer limit (~128KB). This provides clear when-to-use and when-not-to-use guidance, effectively helping the agent select the correct tool.

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