manage_downloads

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

The description contradicts the annotations: it says 'start one' (action=download) which has side effects (creates a file in the Downloads folder), while annotations declare readOnlyHint=true, implying no side effects. Although the description richly describes the saveAs behavior, the contradiction is a serious issue.

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 three sentences long, front-loaded with the main purpose, and each sentence provides relevant detail. It is concise without being terse, though the technical depth might be slightly heavy for a quick scan.

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?

The tool has 5 parameters and no output schema. The description explains the trickiest part (download state) but does not describe the return format for list or wait_for_complete, nor does it mention timeout/limit behaviors beyond what the schema already states. This leaves some gaps for an agent to fully understand expected outputs.

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 descriptions cover all parameters, but the description adds crucial nuance beyond the schema, particularly for action=download: it explains that it reports the real download state and details the waiting_for_user behavior under saveAs prompts. This adds value beyond the structured field 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 states the tool's purpose with specific verbs: 'List downloads, start one, or wait for the newest to finish.' It clearly identifies the resource (downloads) and the three distinct operations, distinguishing it from sibling browser automation tools.

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 gives context ('Files land in the browser Downloads folder, not on the server') but does not explicitly state when to use this tool over alternatives, nor does it mention any exclusions or alternative tools. The usage context is implied but not fully explicit.

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