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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered and the description correctly does not repeat it. What it adds is operational metadata absent from annotations: the GET endpoint and a 5-credit cost at Tier ½, which matters for budgeting calls. It says nothing about response size or whether the 'full' dictionary is paginated, which is the main behavioral unknown for a bulk-return tool.

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 naming the resource and its payload, followed by compact group/endpoint/cost metadata lines. Nothing is redundant. It is arguably under-specified rather than bloated, but every sentence earns its place.

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?

An output schema exists, so return-value structure need not be explained, and the cost/endpoint lines round out the operational picture. The missing piece is disambiguation from four closely named dream siblings and any hint about the volume of a 'full' dictionary response. Adequate for calling it, weak for choosing it.

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% and both optional parameters (fields, precision) are documented in detail with examples and defaults, so the baseline of 3 applies. The description contributes nothing about parameters, though notably it never signals that these are generic response-shaping controls rather than symbol filters — an agent might expect a lookup parameter here.

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 specific resource (a full dream symbol dictionary) and enumerates its content fields: category, element, archetype, common and shadow meanings, and recurring-dream readings. That is far more informative than the bare name. It stops short of a verb (list vs. look up vs. dump) and never distinguishes this 'full' dictionary from siblings like astroway_esoteric_dreams_symbol_keyword, dreams_by_element, or dreams_recurring_themes, which cover overlapping content.

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 guidance at all — no statement of when to pick the full dictionary versus the keyword, element, or recurring-themes variants that sit right next to it in the sibling list. An agent must infer from the word 'full' that this is the broad enumeration and the others are filtered lookups. No prerequisites or exclusions are given.

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