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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely useful non-schema context: the endpoint path and a cost of 5 credits (Tier ½), which an agent needs for budgeting. It says nothing about response size or shape, though an output schema exists to cover that.

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 compact sentence that front-loads the resource and its examples, followed by clearly delineated bracketed metadata for group, endpoint, and cost. No filler prose; the metadata block is terse and skimmable.

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 zero-required-parameter, non-nested, read-only lookup with a 100%-covered schema and an output schema, the description supplies enough to call the tool correctly, and the cost hint covers a real decision factor. A brief note on what the catalogue returns per theme would make it fully self-contained.

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%, so both parameters (fields, precision) are already fully documented in the schema. The description adds no syntax, default, or usage detail beyond that, which is the expected baseline when the schema does the work.

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 (a catalogue of recurring dream themes) and illustrates it with four concrete examples plus the kind of content returned ('universal psychological meanings'). This is clearly distinguishable from siblings like astroway_esoteric_dreams_decode or astroway_esoteric_dreams_symbol_keyword by subject matter, but the description 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?

There is no when-to-use statement, no condition that selects this tool over the many adjacent dream/divination siblings, and no prerequisites. The name and the phrase 'recurring themes' imply it is a reference lookup, but the agent must infer that entirely.

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