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. The description's only added behavioral signal is the cost line ('10 credits (Tier 1)'), which is genuinely useful consumption info not present in annotations, but it says nothing about seeding, randomness, or what an outcome reading contains.

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?

The text is short and front-loaded but that brevity comes from under-specification rather than tight editing; the sentence 'Single outcome card.' plus group/cost tags leave most of the description's job undone.

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 explained, but for a 5-parameter tool with 40% schema coverage and no usage guidance, the definition is far too thin: an agent cannot tell what question/seed/allowReversed do or how this differs from neighboring RWS draws.

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 coverage is only 40%, with seed, question, and allowReversed carrying no schema description, and the description supplies zero parameter meaning. With no required parameters and an unexplained question/seed pair, the description does not compensate for the coverage gap.

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 'Single outcome card' essentially restates the tool name and title ('RWS: Outcome Card') without adding a verb or clarifying what an 'outcome card' is versus a plain single draw. It does convey the scope (one card) but gives no differentiation from close siblings such as astroway_tarot_rider_waite_draw_single, astroway_tarot_rider_waite_shadow_card, or astroway_tarot_rider_waite_clarify.

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, no conditions or exclusions, and no mention of any alternative tool. The reader cannot tell from the description why to pick the outcome card over draw_single or any other single-card RWS tool; only the group tag hints at context.

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