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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the cost/tier metadata (10 credits, Tier 1), which is genuinely useful pre-call information, but says nothing about whether a seed makes the draw deterministic or how reversed cards are handled.

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 short and front-loaded with the core noun phrase first, then metadata tags. Nothing is padded, though the brevity is arguably under-specification rather than discipline.

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 5-parameter tool with 40% schema coverage and no usage guidance, this is thin. The presence of an output schema excuses it from describing return values, but the missing parameter docs and the absent distinction from sibling draw/clarify tools leave real gaps.

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%: seed, question and allowReversed have no schema description, and the description adds no meaning for any parameter. With sub-50% coverage the description is expected to compensate, and it does not — notably it never explains that `question` is the prompt being clarified.

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 deliverable (a single clarifying card) within the Marseille tarot group, but the verb is implicit and it never distinguishes itself from close siblings like astroway_tarot_marseille_draw_single or astroway_tarot_rider_waite_clarify. An agent can infer the resource but not why this differs from a plain single-card draw.

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. Nothing states that this is meant to be drawn after a prior reading to resolve ambiguity, or how it relates to draw_single / draw_three_card. The agent is left to guess the intent from the name alone.

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