fasttransfer_execute_transfer

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

Adds context beyond annotations: safety gate (confirmation=true) and binary installation requirement. Annotations already mark destructive, so description complements well.

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?

Three sentences covering purpose, prerequisite, safety gate, and failure condition. No superfluous information, well front-loaded.

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 2 params, 100% coverage, no output schema, and annotations, description covers execution, prerequisite, safety, and binary check. Could mention result behavior but not critical for usage.

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?

Adds critical semantics beyond schema: command must be unmasked output from preview, not to be modified; confirmation must be explicitly true and require user confirmation. Schema coverage 100% but description enriches usage.

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?

Clear verb 'Execute' with specific resource 'FastTransfer command previously built by fasttransfer_preview_transfer'. Distinguishes from sibling fasttransfer_preview_transfer which builds the command.

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 states the command must come from a prior call, requires confirmation=true as safety gate, and will fail if binary not installed. Implicitly defines when to use vs. preview tool, but no explicit exclusion of other sibling tools.

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