create_meta_download

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

Description discloses the asynchronous background nature and the return of a { guid } for polling, which is essential behavioral context. With no annotations provided, this compensates partially, but it does not state whether the operation is read-only or any side effects beyond creating the export.

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?

Single sentence with no filler, front-loading the key action and return behavior. Perfectly concise.

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 creation tool with 4 params, the description covers the essential process: initiate export, get guid, poll status. It does not detail how to poll or retrieve the final CSV, but the reference to 'poll status' gives adequate direction. No output schema exists, so the return format is stated.

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?

Input schema descriptions cover all 4 parameters with 100% coverage, so baseline 3 applies. The description does not add parameter-specific meaning beyond indicating it's a metadata CSV export, so no additional value.

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?

Description states the specific verb 'kick off' and resource 'background metadata CSV export', clearly distinguishing it from sibling tools like list_meta_downloads and create_download. It also notes the return format, making the purpose unambiguous.

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 initiating a background metadata CSV export but offers no explicit when-to-use guidance or exclusions. Sibling tools like create_download and bulk_download_assets exist, so alternatives are not addressed.

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