licenses_export_async_download

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds timeout behavior (10 min, overridable via env var) and that it returns JSON array. No contradictions.

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 plus a URL, no wasted words. Front-loaded with purpose, then key behavioral details.

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?

Covers return value, prerequisite, timeout, and spec link. Lacks output structure details, but tool is simple and output is a 'JSON array of license records'.

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?

Only one parameter (exportId) with 0% schema coverage. Description does not explain exportId beyond implying it is the export identifier from the status endpoint. Lacks explicit semantic guidance.

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 downloads a completed async license export and returns a JSON array of license records. It distinguishes itself from sibling tools like licenses_export_async_start and licenses_export_async_status.

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?

Explicitly states to call only after the *_status endpoint reports DONE, otherwise a 404 is returned. Also mentions timeout override. Does not explicitly compare with alternatives like licenses_export_sync, but guidance is clear.

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