Browser Downloads

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

No annotations are provided, so the description carries the full burden. It does disclose that configuration is session-scoped and that configure must precede the download trigger, which is useful behavioral context. However, it says nothing about whether the directory is validated, what happens if configure is called twice, or persistence beyond the session.

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 tight sentences, front-loading the capability and then the workflow. Every clause carries information. Slightly dense with the parenthetical example, but no wasted text.

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 two-action tool with no annotations and no output schema, the description covers the essential workflow and even hints at the list output (files and their sizes). Minor gaps remain on error handling and mode interaction, but an agent has enough to invoke it correctly.

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%, so the schema already documents path, action, mode and sessionId, and the enum values are self-describing. The description reinforces that path is the directory for 'configure' but adds no format or constraint detail beyond the schema. Baseline 3 applies.

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 specific verbs and resources: it configures the download destination for the session and lists downloaded files. It is clearly differentiated from all siblings, none of which deal with downloads. It loses a point only because the dual configure/list purpose is slightly less crisp than a single-action tool.

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?

It gives explicit ordered guidance: call action 'configure' once with a directory before triggering a download (e.g. clicking a download link), then action 'list' afterward. The trigger condition and the sequence are both spelled out, leaving nothing to inference.

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