fasttransfer_preview_transfer

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds specifics: password masking, no connectivity test, auto-suggest parallelism. Consistent and adds value beyond annotations; no contradictions.

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?

Single efficient paragraph, front-loaded with main purpose. Every sentence earns its place—purpose, behavior, auto-suggestion, and next step. No redundant text.

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?

No output schema; description only says 'Shows the exact CLI command' without detailing structure. Complex tool with many parameters but description offers limited guidance on parameter usage or typical configurations. Adequate but leaves gaps for full completeness.

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 has extensive parameter descriptions but the overall schema description coverage is only 25%. The description does not compensate by explaining key parameters or providing usage hints beyond mentioning parallelism. Does not add meaning beyond what's in the schema.

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?

Clearly states the tool builds and previews a transfer command without executing it. Uses specific verb+resource (build and preview transfer command) and distinguishes from the sibling fasttransfer_execute_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?

Explicitly advises to pass the command to fasttransfer_execute_transfer after preview. Mentions auto-suggestion of parallelism when not specified, and clarifies what it does not do (test connectivity or execute). Lacks explicit alternatives or when-not-to-use, but context is clear.

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