Latest downloads

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

Annotations already cover readOnly/idempotent/openWorld safety, so the bar is lower, and the description still adds real context: soft98 has no latest listing, results are merged and date-sorted, output is metadata plus item page urls only, and failed sources appear under `errors`. It stops short of describing ordering ties, deduplication, or rate-limit behavior.

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 sentences, zero filler, with the core behavior (newest uploads, merged, sorted) front-loaded and the caveats (soft98 exception, errors bucket) following compactly. Every clause earns its place.

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?

With no output schema, the description correctly discloses the return shape (metadata and item page urls only) and the error surface (`errors`). For a small bounded result set (1-5 per source) this is nearly complete, though pagination/limits and result ordering edge cases are unstated.

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 defaults, ranges, and examples for all three params, so the schema carries the load. The description adds no syntax or format detail beyond referencing source ids and category slugs implicitly, matching the baseline 3 for a fully documented 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?

States a specific verb and resource ('Return the newest uploads of the download sites ... merged and sorted by date'), which is clear and distinct from a search or item-detail tool. It notes the soft98 exception, but never names the sibling tools it differs from (dl_search, dl_item) to explicitly disambiguate.

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?

Usage is implied (browse the latest across sources) but there is no explicit when-to-use or when-not-to-use guidance relative to dl_search or dl_item. The 'Empty = all' semantics for sources and category are documented in the schema, not the description.

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