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 covered. The description adds genuinely useful non-schema context — the group membership and the 10-credit Tier 1 cost — but says nothing about how randomization/seed behaves or how allowReversed affects the draw.

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 short and front-loaded, with the core purpose in the first line and metadata bracketed below. Nothing is padded, though the bracket block is administrative rather than descriptive.

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. However, for a 5-parameter tool with low schema coverage and no usage guidance, the definition leaves the agent guessing about the question/seed/reversed-dimension semantics and about when this tool beats its many siblings.

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 and only 40% schema description coverage, the description carries real explanatory burden and supplies none. It is silent on 'question' (the natural place to state that the querent's question shapes the reading), 'seed', and 'allowReversed', all of which are undocumented or thinly documented in the schema.

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?

It states a single-card draw whose intent is to 'surface hidden information', which gives the agent a rough sense of the tool, but the phrasing is thematic rather than specific about what the tool returns. It is not differentiated from close siblings such as astroway_tarot_rider_waite_draw_single, _clarify, or _shadow_card, which occupy the same conceptual space.

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 stated prerequisites, and no reference to any alternative tool. The agent is left to infer that this applies to situations involving concealed or unknown factors, and nothing tells it how this differs from the other single-card RWS draws.

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