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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description adds value by disclosing the result state machine, including that 'skipped' carries a reason and that 'drafted' implies a draft exists elsewhere. It does not say whether results are ordered or limited, which keeps it off a 5.

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?

One sentence, front-loaded with the resource, then the detail. The status enumeration is the only elaboration and every item earns its place by describing a distinct outcome.

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 carries the burden of return semantics and does so by enumerating the three possible statuses and the optional skip reason. It omits ordering or pagination behavior, which is a real but minor gap for a read-only progress list.

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?

There is a single required parameter at 100% schema coverage, and the schema even tells the caller to use get_status to discover valid values. The description adds no extra meaning about workspaceId, so the baseline 3 for fully documented schemas applies.

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?

Names a specific resource (sites queued via import_sites) and states exactly what is reported about each: waiting, drafted, or skipped with reason. An agent can immediately distinguish it from import_sites (which enqueues) and list_pending_drafts (which shows the drafts produced).

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?

By tying itself to 'the sites queued with import_sites' and pointing at list_pending_drafts for drafts, it makes the natural call sequence (import → poll progress → inspect drafts) clear. It stops short of an explicit 'use this when / do not use this when' statement, so it is a strong 4 rather than a 5.

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