list_downloads

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

The description adds that the tool returns status and saved file path, but annotations already declare readOnlyHint=true. No additional behavioral traits (e.g., pagination, time limits) are disclosed, which would be helpful.

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 a single, well-structured sentence that immediately conveys the tool's purpose. No extraneous information.

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 no output schema, and the description does not explain the structure of returned data beyond mentioning status and path. For a list tool, this omission is noticeable.

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 coverage is 100%, so the description does not need to add meaning to parameters. Baseline 3 is appropriate as the description does not enhance parameter understanding beyond the schema 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 the verb 'List' and the resource 'downloads tracked since startup', including what is returned (status and saved file path). It distinguishes itself from sibling tools like clear_downloads and set_download_behavior.

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 reading download history since startup. While it doesn't explicitly state when not to use it or list alternatives, the context of sibling tools (e.g., clear_downloads, set_download_behavior) makes its purpose clear.

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