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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered without the description. The description adds cost (5 credits, Tier ½) and the endpoint, which is useful call context, but it does not disclose anything further about response size, pagination, or limits.

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?

A single front-loaded sentence describes the payload, followed by a compact metadata block (group, endpoint, cost). There is no filler, though the bracketed metadata is somewhat mechanical and could be trimmed.

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 low-complexity read tool, the essentials are present: annotations carry safety, a 100%-covered 2-param schema carries inputs, and an output schema exists so return values need no prose. The only real omission is routing guidance versus the four sibling dream tools.

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 100%, with both optional compact-mode parameters ('fields' and 'precision') fully documented in the schema itself. The description adds no parameter meaning, so the baseline 3 for schema-covered parameters 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 names a concrete resource ('full dream symbol dictionary') and enumerates its contents (category, element, archetype, common/shadow meanings, recurring-dream readings), so an agent knows what it returns. The word 'Full' hints it is the complete dictionary rather than a lookup, but no sibling is named to make the distinction explicit, which keeps it at a 4 rather than 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?

There is no when-to-use statement and no alternatives surfaced. Siblings such as astroway_esoteric_dreams_symbol_keyword, astroway_esoteric_dreams_decode, astroway_esoteric_dreams_by_element_element, and astroway_esoteric_dreams_recurring_themes overlap heavily, yet the description gives no rule for choosing among them.

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