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

Annotations already declare non-readonly, non-idempotent, open-world behavior. The description adds real context beyond that: a 2-minute global cooldown, an auth prerequisite (Privi pass), per-call billing through x402, and the side effect of rewriting speed rankings. It stops short of describing failure modes or actual cost, deferring to quantum_pricing.

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?

Three tight sentences: the action first, then the cooldown, then the auth/payment prerequisites. Every sentence carries information, though the pricing pointer could be folded more tightly into the prerequisite sentence.

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 mutating, billed, rate-limited tool with a single parameter and no output schema, the description covers action, side effect, throttling, auth, and cost routing. What an agent still lacks is return-value expectation or what happens when the cooldown is hit.

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 coverage is 100% and the single parameter already documents that it comes from inspector_pass. The description only restates 'Requires a Privi pass,' adding no format or acquisition detail beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource with scope: 'Run the standard 8-qubit benchmark on every active realm at once and update Privilege's speed rankings.' That is clearly distinct from a single-realm benchmark. It does not explicitly name a sibling (e.g. quantum_benchmarks) to contrast against, so it falls just short of 5.

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?

It states concrete preconditions and constraints (Privi pass required, at most once every 2 minutes, paid via x402 when payments are on, see quantum_pricing), which implies when the tool is usable. However, it never says when to choose this over quantum_benchmarks or quantum_leaderboard, and gives no when-not-to-use guidance.

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