appium_mobile_file

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

Annotations already declare readOnlyHint=false and openWorldHint=false, so the safety profile is partly covered. The description adds that pull returns contentBase64 (useful return-shape context), but omits the two-step CONFIRMATION REQUIRED flow documented only in the schema and says nothing about overwriting existing device files or permission needs.

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?

Two short sentences, zero filler, and the primary capability is front-loaded before the per-action data requirements.

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?

With no output schema, noting the contentBase64 return is valuable, but the definition stays silent on the confirmation-token workflow and on overwrite/destructive semantics for push — meaningful gaps for a file-write tool with five parameters.

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 every parameter is already documented, including action, remotePath formats, and the confirmToken requirement. The description's 'action=push uses payloadBase64' restates exactly what the schema says, adding no new syntax or format detail, so baseline 3 applies.

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?

States a specific verb ('Push or pull') and resource ('a file') scoped to Appium mobile extensions, and names both modes. No sibling tool performs file transfer, so differentiation is de facto clear, though it never explicitly says it is the only/right tool for this job.

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?

The push/pull split implies when each mode applies (upload vs. download), but there is no explicit 'use this when' guidance, no prerequisites, and no mention of the confirmation handshake that governs push.

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