list_meta_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 mentions 'background' and 'List', hinting at async jobs, but does not disclose response format, pagination behavior, or access requirements. It does not explicitly state that the operation is read-only, though listing implies it.

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 sentence with no filler, front-loaded with the verb and resource. Every word 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?

For a simple list tool, the purpose and basic parameters are covered. However, without annotations or an output schema, more detail would be valuable—such as what fields a job includes, whether results are paginated (implicit via per_page), and any behavioral notes.

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 75% (page, dates, per_page documented). The description adds no parameter context beyond what the schema provides. The undocumented user_id parameter is not compensated for in the description.

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 uses a specific verb 'List' and resource 'background metadata-export jobs', clearly indicating the operation. It distinguishes this from sibling tools like list_meta_imports (imports vs exports), though it does not explicitly name alternatives.

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?

There is no guidance on when to use this tool versus alternatives such as list_meta_imports or get_meta_download_columns. The description does not mention filtering, pagination, or whether it lists all jobs or only the caller's.

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