licenses_export_async_status

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds only 'Poll status', which aligns with readOnly. No additional behavioral traits (rate limits, response structure) are disclosed beyond annotations.

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 concise: one sentence and a URL link. It is front-loaded with the core action. The link adds context but is not essential. No extraneous information, though the link could be integrated or omitted for brevity.

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 polling endpoint with one parameter and no output schema, the description covers the basic purpose. However, it lacks details about the response (e.g., status values, polling strategy) which would help an agent know when to stop polling. The external spec link partially compensates.

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 sole parameter exportId has no description in the schema or tool description. The description does not explain where to obtain the exportId (e.g., from a prior start call). Given 0% schema coverage, the description should compensate but fails to do so.

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 'Poll status of an async license export job' with a specific verb ('poll') and resource ('async license export'). This distinguishes it from sibling tools like licenses_export_async_start (start) and licenses_export_async_download (download).

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 explicit guidance on when to use this tool versus alternatives (e.g., sync export or status of other async jobs). The context implies it should be called after starting an export and before downloading, but this is not stated directly. There is no mention of polling intervals or completion conditions.

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