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

No annotations are provided, so the description carries full behavioral disclosure burden. It discloses the 20MB decoded size hard cap, the metacharacter restriction on remotePath, and the return shape { ok, remotePath, sizeBytes }. It doesn't mention auth/permissions needs or overwrite behavior, but the disclosed constraints are meaningful and beyond basic expectations.

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?

Four dense sentences with zero waste. Each sentence carries distinct useful information: operation+format, allowed destinations, size cap+security constraint, and exception routing with return shape. Front-loaded with the primary action.

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 a 3-param tool with no output schema and no annotations, the description covers operation, encoding, destination constraints, size limits, security notes, alternative routing, and return format. It could mention overwrite behavior or permission requirements, but for a file-push utility the coverage is solid and practical.

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 baseline is 3. The description adds value beyond the schema: it clarifies content is base64-encoded (matching the schema's description but reinforcing encoding format), specifies the 20MB decoded cap interpreting content size, and explains remotePath's constraints (no shell metacharacters, must be an allowed absolute path). This adds genuinely useful semantics.

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 'Push a base64-encoded file to the device' with a specific verb+resource pairing. It distinguishes this from device_file_pull (pull direction) and app_install (for APKs explicitly), and the sibling list contains both device_file_pull and app_install, showing intentional differentiation.

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?

Provides explicit when-to-use guidance including allowed destinations (/sdcard/, /data/local/tmp/), what those dirs are for (frida-server, tcpdump), hard size cap, metacharacter constraint, and explicitly directs APK cases to app_install instead. This is strong when/when-not guidance.

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