files

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

The description adds real behavioral context the annotations do not: pull never overwrites, push is refused if the target already exists, and 'Rien n'est jamais effacé'. However, that last cluster directly conflicts with the annotation destructiveHint=true, so the agent receives contradictory signals about whether the tool can destroy data. Flagged as an annotation contradiction.

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?

One front-loaded paragraph states the resource first, then breaks each action into a labelled clause ('list :', 'pull :', 'push :'), so it scans quickly despite being dense. Every clause carries information (defaults, overwrite policy) rather than filler. Minor density cost only.

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-parameter tool with no output schema and 0% schema coverage, the description covers actions, defaults, overwrite/delete policy and path direction, which is most of what an agent needs. It does not describe what list returns (fields, recursion) or error behaviour, a modest remaining gap.

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 0%, so the description must carry the parameters, and it largely does: it defines action's three values, explains that path is the source file (on the phone for pull, on the PC for push), and gives per-action defaults for dest (~\Downloads\Telephone for pull, /sdcard/Download for push/list). It only leaves the exact meaning of path for list slightly implicit.

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 names a specific resource (the phone's shared storage: /sdcard, DCIM/Camera, Download, Documents) and enumerates the three concrete operations (list, pull, push) with their direction of transfer. An agent immediately understands this is a phone-file manager. It stops short of 5 because it never contrasts itself with any sibling tool (e.g. 'phone').

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?

Each action is given a clear use context: list reads a folder's contents (default /sdcard/Download), pull copies phone→PC, push copies PC→phone, and the defaults per action are stated. This tells the agent which action fits which task. There is no explicit when-not-to-use guidance or named alternative, so it is not a 5.

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