List Downloads

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

With no annotations, the description carries the full disclosure burden and delivers very little: only ordering ('newest first'). It does not say whether results are paginated, how far back 'recent' reaches, whether cancelled or failed jobs appear, or whether the call is cheap. An output schema exists, but input-side behavior remains undisclosed.

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?

Nine words, front-loaded with the resource and ordering — nothing wasted, but the brevity comes at the cost of under-specification rather than achieved efficiency. There is no second sentence to carry usage or parameter context.

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 an output schema (so return values need no explanation) and one parameter, the description could have covered ordering semantics, limit behavior, and how this differs from download_status. Instead it covers only ordering, which is insufficient for a listing tool with zero annotation support.

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 single parameter 'limit' is undocumented in the schema (0% coverage) and the description says nothing about it. A default of 10 and the 'recent' framing suggest bounded retrieval, but whether limit caps jobs returned, how to request more, or if any paging token exists is left entirely unstated.

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 fragment 'Recent download jobs, newest first' identifies the resource (download jobs) and the ordering, but it is a noun phrase with no verb and never states that it returns a list. Siblings like download_status and download_programme are not differentiated, leaving the agent to infer that this enumerates jobs while those target a specific one.

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?

No when-to-use guidance, no prerequisites, and no reference to any sibling tool. The agent is not told how this differs from download_status or when to prefer it. Only the implicit 'recent' framing hints at a use case.

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