preset_fab_download

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

No annotations are provided, so the description must convey behavioral traits. It only says 'downloads via legendary' without disclosing aspects like blocking behavior, overwrite policy, authentication needs, or progress indication. This is insufficient for a download tool.

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 brief and to the point, with a structured args section. It avoids unnecessary words but could include more detail without losing conciseness.

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 no output schema, no annotations, and 0% schema coverage, the description is severely incomplete. It does not mention return values, error handling, file size limits, or any operational context, leaving the agent without crucial information.

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 description explains that app_name is the identifier from preset_fab_list_vault, adding value beyond the schema. However, the destination parameter receives no explanation, and overall schema coverage is 0%, so the description only partially compensates.

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 an asset from the Epic vault using 'legendary', which is a specific verb and resource. It is distinct from sibling tools like preset_fab_list_vault (listing) and preset_download_url (different source).

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 indicates that app_name comes from preset_fab_list_vault, providing a prerequisite. However, it does not explicitly state when to use this tool over alternatives or when to avoid it, leaving room for ambiguity.

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