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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by asserting determinism (same results as the site's shared engine) and declaring unit conventions, but says nothing about validation behavior, error modes, or how defaults are resolved.

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 tight sentences with no filler, and the core function is front-loaded before the disclaimers. Every clause carries information an agent would otherwise have to guess.

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?

An output schema exists, so return values needn't be explained, and the safety picture is covered by annotations. But for a tool taking a 25-field nested input with zero field-level descriptions, the description is far too thin to let an agent populate inputs correctly.

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?

Reported schema coverage is 0% for a nested object with roughly 25 fields, many of them enums whose semantics are non-obvious (quantization vs. quantization_bits, quantization_memory auto/pinned/cached/cold, product_compression, the on_disk/mmap family). The description only clarifies the KiB-in/byte-out unit convention, leaving the bulk of the parameter space undocumented in both schema and description.

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 specific verb and resource ("Calculate deterministic Qdrant capacity") and names the engine it uses, which is far more informative than a bare name restatement. It also draws a boundary ("not measured capacity or QPS sizing"), though it doesn't name a sibling tool to route to.

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?

"not measured capacity or QPS sizing" implies a when-not-to-use condition, which is more than most definitions offer. However, no alternative tool (e.g. compare_accelerators, list_qdrant_pricing) is named for the excluded cases, and no prerequisites are stated.

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