Recurring Dream Themes

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add content-level context, which it does: it names the themes covered and the endpoint/cost (5 credits, Tier ½). It does not say whether the list is static/complete, a minor gap.

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?

One front-loaded sentence carries the payload, followed by compact endpoint/cost metadata lines. No filler or repetition; appropriately sized for a zero-argument reference tool.

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?

With an output schema present, the description needn't explain return values, and for a no-param read-only lookup it covers what an agent needs to select it. Only the routing guidance to sibling dream tools is absent.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate and it correctly makes no parameter claims.

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 resource ('catalogue of common recurring dream themes') and gives concrete examples (falling, naked in public, losing teeth, being chased) plus the meaning it attaches. This distinguishes it implicitly from the dreams_decode/symbol_keyword siblings that act on a user-supplied image or keyword, but it never names those alternatives.

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 only implied: the word 'catalogue' signals a reference/lookup tool rather than a decode tool, but there is no explicit statement of when to pick this over astroway_esoteric_dreams_decode or astroway_esoteric_dreams_symbol_keyword, nor any prerequisites.

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