preset_fab_download

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

No annotations are provided, and the description lacks details on side effects, authentication needs, whether downloads are synchronous, or any constraints. It only states the basic action.

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 very short and to the point, with the purpose in the first sentence. However, it could be improved by also briefly explaining the destination parameter.

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 tool's role in a workflow (downloading from vault) and no output schema, the description lacks details on expected outcomes, error cases, and how destination affects behavior. It only covers the bare minimum.

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 the app_name parameter (identifier from preset_fab_list_vault) but does not mention the destination parameter, which is optional with default null. With 0% schema coverage, the description should cover both parameters.

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 explicitly states the tool downloads an asset from the Epic vault using 'legendary', with a clear verb and resource. It differentiates from sibling tools like preset_fab_list_vault.

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 implies the tool should be used after preset_fab_list_vault by noting that app_name comes from that tool, but it doesn't explicitly state when to use this tool versus alternatives like preset_download_url.

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