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 description is not needed for the safety profile and adds no behavioral context of its own (aggregation granularity, scoping, freshness, auth requirements). The only extra content is the pointer to describe_operation, which is a discovery hint rather than behavioral disclosure.

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 content sentence is repeated twice verbatim, which is pure waste, and the remaining text is a bare operation ID. There is no front-loaded statement of intent, so the definition is both redundant and under-specified rather than concise.

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, no parameter documentation, and free-form nested query/params objects, the description should explain the response shape (what 'stats' means) and the query contract. Instead it defers entirely to describe_operation, leaving the agent without enough to invoke the tool confidently beyond a parameterless call.

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% and both parameters ('query' and 'params') are untyped free-form objects with no enumerated keys, so the description must compensate — yet it says nothing about what can go in query or params. The 'describe_operation' pointer is the only indirect help, which is far below what an agent needs to construct a valid call.

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 path, which duplicates the title and tool name verbatim ('pending-imports: GET /api/pending-imports/stats'). There is no statement of what the stats contain or what question the tool answers, so the agent cannot distinguish it from siblings such as get_pending_imports_35de5e1fb42a10d549a1ca45 or get_pending_imports_by_batchId_percenta_ba6827ae6a73cce2f8058b64 beyond guessing from the URL.

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 when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The only actionable hint is that 'describe_operation provides native request schemas', which tells the agent to consult another tool but not when this particular endpoint is the right choice over the sibling list/count endpoints.

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