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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so safety is covered. The description adds genuinely useful non-schema context in the cost line (10 credits, Tier 1) and the group tag, but says nothing about whether seed makes the draw deterministic, or how question/allowReversed affect the reading.

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?

It is brief and front-loaded, but the brevity comes from omission rather than efficiency: two words of purpose plus a metadata block that is not the definition's core job. Nothing is padded, yet the single sentence does not earn its place as a full definition.

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 with 5 parameters, 40% schema coverage, and no usage or sibling differentiation, the definition is not complete enough for an agent to invoke it correctly versus the many adjacent RWS 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 only 40%: fields and precision are documented, but seed, question, and allowReversed carry no schema descriptions, and the description adds nothing about any of them. For a 5-parameter tool with an undocumented randomness/context surface, this leaves the agent guessing.

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?

"Single advice card" gives a rough verb+resource, but it never says it draws/draws-a-card from the RWS deck nor distinguishes itself from near-identical siblings like astroway_tarot_rider_waite_draw_single, _outcome, or _clarify. An agent could pick the wrong RWS one-card tool without opening the schemas.

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, when-not-to-use, or alternative guidance at all. With dozens of sibling RWS draw/interpret tools, the description gives no condition that selects this one over the others.

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