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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing behavioral beyond the route — no indication of what a 'pending import' record contains, whether a missing batchId 404s, or result size.

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 single sentence is duplicated verbatim, wasting the reader's attention, and the remaining content is an operation ID plus a pointer rather than front-loaded substance. Short but not economical.

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 return values, and it does not; it also gives no vocabulary for 'pending import' records. The one redeeming element is the explicit pointer to describe_operation, which tells the agent where to obtain the real request schema, but overall it leaves the tool's behavior underspecified.

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%, with two parameters (including a nested params object) and no field documentation anywhere. The description never explains what batchId refers to, its format, or what the optional query object is for, so it fails to compensate for the coverage gap; the redirect to describe_operation is only a partial mitigation.

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/pending-imports/:batchId' twice, which is essentially a tautology of the name/title rather than a statement of what the tool returns or why an agent would call it. It also fails to differentiate from close siblings such as get_pending_imports_by_batchId_percenta..., get_pending_imports_by_batchId_rent_tie..., and get_pending_imports_by_batchId_source_d..., which all share the same batchId path shape.

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?

The only guidance is 'describe_operation provides native request schemas', which is a pointer to a sibling, not a when-to-use rule. There is no statement of when this general batch lookup is preferred over the percentage/rent-tie/source-detail siblings.

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