move-file-to-location

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

With no annotations, the description must disclose behavioral traits but states only the action 'move' without explaining side effects, required permissions, or confirmation behavior. It does not mention whether overwriting occurs, what happens to the original, or any error conditions. This leaves significant behavioral uncertainty.

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?

The description is short and front-loaded with no wasted words, which is structurally concise. However, it under-specifies by omitting essential details about the destination and parameters, making it too terse to be fully useful.

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?

Given the minimal schema (1 param, no descriptions) and lack of output schema or annotations, the description should thoroughly explain the tool's behavior and parameter semantics. It fails to define what 'location' means, how the folder parameter relates to it, or any expected return values, leaving the tool incomplete for an agent to use correctly.

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?

The schema has one parameter 'folder' with 0% description coverage, and the description adds no meaning for it. The tool description does not mention the folder parameter at all, so the agent cannot infer that 'new location' refers to a folder ID. This is a critical gap for correct invocation.

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 the verb 'Move' and the resource 'a file', making the primary purpose understandable. It also distinguishes from sibling tools like add-file or update-file-by-id by implying a relocation action. However, it leaves 'new location' vague without clarifying it refers to a folder destination.

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 description provides no guidance on when to use this tool versus alternatives, such as update-file-by-id or copy operations. There are no use-case scenarios, prerequisites, or exclusions mentioned. Users are left to infer when moving a file is appropriate.

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