list_cached

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

Annotations already indicate readOnlyHint=true, so the description adds value by detailing the modes and their effects on the manifest and cache. However, it does not explicitly state that no data is modified, which is already implied by readOnlyHint.

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 two sentences with front-loaded purpose. Each sentence earns its place: the first states the core action, the second explains the parameter options. No redundant 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?

Given the presence of an output schema and annotations, the description covers most necessary information. The only minor gap is the insufficient explanation of the download_dir parameter, which is not critical but could be clearer.

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 description explains the cache_mode enum values in detail, compensating for the 0% schema description coverage. However, download_dir is only vaguely described as 'within the selected download_dir', leaving its purpose and default behavior unclear.

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 lists cached downloads without network access, and explains three modes (index, refresh, rescan) with distinct behaviors. This distinguishes it from sibling tools like fetch_paper that access the network.

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 offline listing but does not explicitly state when not to use it or provide alternatives (e.g., use fetch_paper for fresh data). The sibling tool names are available but not referenced.

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