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 fully covered. The description adds that the tool explains matching rationale ('and why'), which is a genuine behavioral detail beyond the annotations, but says nothing about cost, limits, or how the matching verdict is computed.

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 short sentences, front-loaded with the capability and followed by the diagnostic use case; no filler. Slightly terse given that two of three parameters go unexplained, but the size itself is appropriate.

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?

For a 3-parameter diagnostic tool with no output schema and 0% schema coverage, the description should carry the burden of explaining mode and criteria but does not. An agent can guess the purpose but cannot confidently construct a correct call, so the definition is materially incomplete.

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 3 parameters. The description only obliquely covers printer_id ('a specific printer'); neither 'mode' (a single-value enum 'autoprint') nor 'criteria' (a string array whose semantics are entirely undefined) is explained anywhere, so the agent cannot know what values to supply.

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?

States a clear verb ('Show') and a specific resource ('queue items match/miss a specific printer') plus the explanatory output ('and why'), which is more specific than the name alone. Sibling differentiation is only implicit — it does not name list_queue, get_queue_item, or match_file_to_printers, which are adjacent tools an agent would compare against.

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?

'Useful for diagnosing why a queue item will not print' gives a concrete use case, so the intent is inferable. However, there is no explicit when-not guidance and no routing to alternatives such as match_file_to_printers or get_queue_item, so the agent must infer the boundary itself.

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