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 of behavioral disclosure. It explains the effect of each behavior (silent save, cancel, reset) and mentions the requirement of a recent Firefox, adding transparency about the tool's operation. It doesn't state persistence or effects on existing downloads, but the core traits are disclosed.

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?

Two concise sentences front-load the purpose and then provide key details. Every sentence earns its place with no fluff.

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 single-parameter tool without output schema, the description explains the modes, the dialog effect, and a prerequisite. It lacks persistence semantics and potential side effects, but overall it is sufficient for straightforward 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?

Schema description coverage is 100%, with the enum values already explained in the parameter description. The tool description adds marginal detail like 'save silently to the default download directory' and dialog avoidance, but the parameter semantics are largely redundant with the schema.

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 the tool controls download handling with three explicit modes (allow, deny, reset) and notes it avoids the native save-file dialog. This verb+resource framing is specific and differentiates from download-list tools like list_downloads, though it doesn't name alternative tools explicitly.

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 usage for setting download policy but does not explicitly state when to prefer this over sibling tools like accept_dialog. 'Requires a recent Firefox' gives a prerequisite, and 'Avoids the native save-file dialog' provides context, but no exclusions or alternatives are mentioned.

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