set_download_behavior

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

With no annotations provided, the description carries the full burden. It discloses the effect (avoiding dialog, requiring Firefox) but does not detail whether changes are immediate, persist, or affect in-progress downloads. It is adequate but not exhaustive.

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 extremely concise: two sentences deliver the purpose, options, side effect (avoiding dialog), and a prerequisite. No superfluous words.

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?

For a simple tool with one parameter, the description covers the main behavior and a key prerequisite. It could mention that the setting persists until changed, but it is largely complete.

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 schema already covers the parameter with a description. The tool description adds explanatory context like 'save silently to the default download directory' and 'reset to default', enhancing understanding beyond the schema's brief descriptions.

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 that the tool controls download handling with three modes: allow, deny, or reset to default. It distinguishes itself from sibling download tools like list_downloads and clear_downloads by focusing on behavior control.

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 mentions that it avoids the native save-file dialog and requires a recent Firefox, giving context for when to use it. However, it does not explicitly state when not to use it or compare with alternatives beyond the implied contrast with other download tools.

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