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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered by structured data. The description adds essentially nothing beyond the route, not describing what status values are returned, polling behavior, or error cases.

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 of the three sentences are a verbatim duplicate of the same route path, which is pure waste. The operation ID mention is boilerplate rather than useful content.

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?

This is a status-lookup endpoint with no output schema, an undocumented required identifier, and a nested-object query parameter; the description supplies none of the information needed to call it correctly or interpret the result.

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?

Schema description coverage is 0% for 2 parameters, and the description provides no explanation of the required importId (format, where it comes from) or the optional query object. With the schema carrying no descriptions, the description should compensate but does not.

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 only restates the HTTP route 'GET /api/import/status/:importId' twice, which does convey a verb and resource but is essentially tautological with the title. It gives no differentiation from closely-related siblings such as get_pending_imports, get_import_history, or get_ai_import_by_batchId.

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?

There is no statement of when to use this tool versus alternatives like the pending-imports or import-history endpoints. The only extra pointer is to describe_operation for native request schemas, which is not usage guidance for choosing this tool.

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