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 genuinely new behavioral context: calls are billed via x402 when payments are enabled, with a pointer to quantum_pricing. It stops short of noting what happens on payment failure or whether results are paginated.

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 with zero padding, and the primary capability is front-loaded before the payment caveat. Every clause carries information an agent needs.

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 read-only list/detail tool with annotation-covered safety and mostly documented parameters, the description covers purpose, mode selection and billing. The remaining gap is minimal: it does not say what the list form returns versus the 'full result' of a single job, though no output schema exists to carry that.

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 80%, so the schema already documents job_id, scape_id, scape_key and the Privi pass requirement. The description only restates the job_id mode switch and says nothing about 'limit' (default 20, max 100), so it adds little beyond structured fields.

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?

Names a specific resource (jobs for a Dream Scape) and clearly states the two modes: a recent-jobs list, or a single job with its full result. It is distinguishable from siblings like dreamscape_submit and dreamscape_open, though it never explicitly contrasts itself with them.

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?

Usage is implied rather than stated: supplying job_id selects the single-job form, omitting it yields the recent list (echoed from the schema). There is no explicit when-to-use guidance against sibling tools and no statement of prerequisites beyond the payment note.

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