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

Annotations already establish readOnly, idempotent, non-destructive, closed-world semantics, so the bar is low. The description adds genuinely useful context beyond them: the precondition that only complete R2 images are attachable, and the disclosure that temporary source URLs and provider errors are never surfaced in the response.

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?

Three short sentences, front-loaded with the core action. The two trailing sentences are relevant behavioral context rather than filler, though they could be tightened.

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?

With no output schema, the description should describe what a status response contains (e.g., import progress or completion states). It tells the agent what is never returned but not what the status actually reports, leaving a real gap for a status-polling tool.

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 asset_id has 0% schema description coverage (type integer, minimum 1 only). The description says the asset is "owned" but never explains what an asset ID is, where it comes from (e.g., returned by import_image), or what form it takes, so it does not compensate for the schema gap.

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 states a clear verb and resource ("Read the owned asset status"), and the title narrows it to image import checking. It does not, however, differentiate itself from sibling get_operation_status, which an agent could plausibly reach for instead.

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?

"Only complete R2 images may be attached" is a downstream constraint, not guidance on when to call this tool versus list_assets, get_operation_status, or import_image. There is no when-to-use, no polling advice, and no mention of alternatives.

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