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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely new information — the 10-credit Tier 1 cost — which an agent cannot get from the annotations or schema. It does not, however, explain whether the draw is randomized, how seed influences reproducibility, or what allowReversed does to the result.

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?

Extremely tight: one sentence of purpose followed by bracketed group/cost metadata and the alias note, with the purpose front-loaded. Every element is short, though the group/cost tags are more metadata than prose and slightly fragment the read.

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 values need not be described, and the cost/alias notes cover the billing and identity concerns. But for a 5-parameter tool with weak schema coverage, the description omits any guidance on question, seed, or allowReversed, leaving real gaps for correct invocation.

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?

With 5 parameters at only 40% schema description coverage, seed, question and allowReversed are undocumented in the schema and the description says nothing about any of them. The description therefore fails to compensate for the coverage gap, leaving an agent unable to tell whether question affects the draw or what allowReversed changes.

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 artifact — a 5-card spiritual development spread — and identifies the deck lineage (Rider-Waite-Smith) via the group tag, which distinguishes it from sibling draws like draw_chakra or draw_shadow_work. It also discloses that it is an alias for astroway_tarot_rider_waite_draw_spiritual_path, so an agent knows the two are the same operation. It stops short of saying explicitly that it draws cards, relying on the alias name to convey the verb.

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 statement of when to pick this spread over the many other RWS spreads (three_card, celtic_cross, horseshoe, decision, year_ahead, etc.) and no prerequisites or exclusions. The only routing signal is the group/cost metadata, which tells the agent nothing about appropriateness of use.

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