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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. Beyond that the description adds nothing behavioral: no indication of pagination, filtering defaults, result volume, or whether 'pending' means awaiting approval, awaiting processing, or errored.

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 path sentence is literally duplicated, and the operation ID adds noise. The one useful sentence (the describe_operation pointer) is buried at the end rather than front-loaded.

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?

No output schema exists, so the description should explain the shape of returned pending imports, yet it says nothing. Combined with an opaque nested query object and no return-value or filtering context, an agent cannot confidently invoke this tool from the definition alone.

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?

With two parameters at 0% schema description coverage and a free-form 'query' object with additionalProperties, the description must compensate — instead it offers only 'describe_operation provides native request schemas'. That is a pointer, not parameter semantics; supported filters, pagination keys, and the empty 'params' object are left unexplained.

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 merely restates the tool name and HTTP path ('GET /api/pending-imports') twice, never explaining what a pending import is (queued import batches? files awaiting processing?) or what the listing returns. It differentiates from siblings only implicitly via the endpoint path, and the operation ID is an internal identifier with no semantic value to an agent.

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 guidance on when to call this versus closely related siblings such as get_pending_imports_stats, get_pending_imports_by_batchId, or get_import_history. The one actionable hint is that describe_operation provides native request schemas, which is a schema-discovery pointer rather than usage guidance.

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