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

Annotations already declare non-read-only, non-idempotent, open-world, non-destructive, so the safety profile is covered. The description adds real context beyond that: per-call billing through x402, persistence of results in the scape, and a hard auth requirement (Privi pass). It does not disclose what happens on timeout or whether a failed job is billed.

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 the core action front-loaded and the billing caveat second. No filler, though the parenthetical cross-reference is doing work that a fuller sentence could do more clearly.

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 an 11-parameter, non-idempotent job-submission tool with no output schema, the description leaves major gaps: no return value (job id? handle for dreamscape_jobs?), no explanation of the tuning knobs, and no failure/timeout behavior. The agent can call it but cannot predict what comes back.

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 only 55% across 11 parameters, and the description compensates for almost none of it. Six parameters (mode, shots, fanout, layers, hedge_ms, deadline_s) have no description anywhere, and the description only points at quantum_pricing and quantum_problems rather than explaining problem/data semantics.

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 ('Run a quantum job in your Dream Scape') and adds a distinguishing scope clause ('keep the result there'), which separates it from siblings like dreamweaver_run and quantum_run_circuit. It stops short of naming those siblings explicitly, so the differentiation is implied rather than stated.

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?

Gives useful preconditions — payments via x402 when enabled, and a Privi pass from inspector_pass — but never says when to choose this over dreamweaver_run, quantum_run_circuit, or quantum_optimize. The agent must infer the selection rule from the 'keep the result there' phrasing.

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