files

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

Adds substantial behavior beyond the annotations: 'Nothing is ever deleted' and 'never overwrites' corroborate destructiveHint=false, while the PC-side allowlist, the confirm=true authorization requirement, and the hard exclusions (.ssh, .env, Windows startup) are safety semantics the annotations do not convey. No contradiction with readOnlyHint=false/idempotentHint=false, since these are file writes.

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?

Front-loaded with the resource and action menu, and nearly every clause carries actionable constraint. The final PC-side line is telegraphic to the point of near-ungrammaticality ('keys, secrets (.ssh, .env…) and Windows startup never'), which costs a little clarity for its density.

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?

Covers scope, defaults, refusals, and safety boundaries well for a 4-parameter mutation tool with no output schema. It does not describe what list returns (formats, entry metadata) or how pull reports success, so an agent has modest remaining uncertainty about results.

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?

With 0% schema description coverage the description must carry all four parameters, and it mostly does: dest and path are explained per action, including the role swap (path = PC file and dest = phone folder for push; the reverse intent for pull), plus confirm's meaning as the user's explicit order. The path/dest distinction is slightly compressed and easy to misread.

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?

Names the resource (phone shared storage, with concrete paths like /sdcard/DCIM/Camera) and enumerates the three operations with a specific verb each: list, pull (phone→PC), push (PC→phone). This is unambiguous and clearly distinct from siblings such as clipboard, capture, or look.

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?

Gives concrete defaults per action (/sdcard/Download, ~\Downloads\Telephone) and states refusal conditions ('refused if it already exists', confirm=true required outside the free PC folders). It stops short of explicitly contrasting the three actions against alternatives, but the per-action routing is clear enough to select correctly.

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