files

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

With no annotations, the description carries the burden and does meaningful work: it states pull never overwrites, push is refused if the destination already exists, and nothing is ever erased — a real safety profile. It omits permission/auth requirements, rate limits, and error behavior, so it falls short of fully transparent.

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 location, then three compact action clauses, then a one-line safety guarantee. Dense but well organized; a couple of parenthetical defaults could be tightened, but no sentence is wasted.

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, zero-annotation tool with no output schema, the description covers all actions, per-action defaults, and destructive-behavior guarantees. Remaining gaps are the return shape of list and any permission prerequisites, but the operational essentials are present.

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 0%, so the description must compensate, and it largely does: it explains that path is the source file for pull/push and dest changes meaning by action (PC folder for pull, phone folder for push), including defaults for each. It does not explicitly state that path is ignored for list, a minor gap.

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 concrete resource (shared phone storage at /sdcard) and enumerates the three specific operations (list, pull, push) with concrete path examples. An agent can immediately tell this tool manages files on the device, and no sibling (look, info, settings, phone, messages, etc.) overlaps with file transfer.

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 tied to a use case: list reads folder contents, pull copies phone→PC, push copies PC→phone, each with a stated default directory. It stops short of explicit exclusions or naming an alternative tool, but the action-level routing is clear enough for selection.

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