RWS: Yes/No

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 two useful pieces of context not in the schema: that the verdict is derived from 'card affinity' and that the call costs 10 credits (Tier 1). It says nothing about whether the question is required for a meaningful verdict.

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 functional sentence is front-loaded and free of padding; the endpoint/group/cost block is terse metadata. Slightly under-specified rather than verbose, but nothing is wasted.

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 and annotations exist, so return values and safety need not be described. However, for a 4-parameter tool with 25% schema coverage, the description leaves the caller without guidance on the 'question' input and how it affects the yes/no/maybe outcome.

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 25% (only 'art' is documented), so the description must compensate and does not. The 'question' parameter, which is clearly the core input for a decision draw, and 'seed'/'allowReversed' are never mentioned or explained in the description.

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 operation ('Single-card draw') and the distinctive output ('yes/no/maybe verdict from card affinity'), which separates it from the sibling astroway_tarot_rider_waite_draw_single that shares the same deck and card count. It never names that sibling explicitly, so the differentiation is implicit rather than stated.

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?

The yes/no/maybe framing implies the use case (a binary decision question), but there is no explicit 'use this when... instead of draw_single/outcome/advice' guidance and no prerequisites stated. An agent must infer the routing from the phrase 'decision' alone.

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