fflDownload

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

With no annotations, the description carries full burden. It discloses WebRTC P2P usage, resume capability, authentication modes, and proxy support. However, it does not mention potential file overwriting or error conditions.

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 well-structured with headings and an Args section. It is front-loaded with the core purpose. Minor verbosity in parameter listing is justified by complexity, but every sentence earns its place.

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 10 parameters, no annotations, and an output schema, the description covers return value, authentication scenarios, and network protocol choice. Missing enableReporting and error handling details prevent a perfect score.

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 description must compensate. It explains 9 of 10 parameters (missing enableReporting) with meaningful context beyond schema types, such as 'Resume incomplete download' and 'Recipient authentication mode required by sender.'

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 it downloads a file from a FastFileLink or HTTP(S) URL, distinguishing between the two modes. The verb 'download' and resource 'file' are specific, and it differentiates from sibling tools like fflShareFile.

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 explains when to use FastFileLink vs regular URLs but does not explicitly state when not to use this tool or mention alternatives like fflShareFile for uploading. Context is clear but lacks explicit exclusions.

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