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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description adds the cost tier (10 credits, Tier 1), which is genuinely useful pre-call context, but says nothing about how the pair is computed or what inputs influence it.

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, but the brevity is achieved by omitting necessary information rather than by precision. The bracketed metadata tags are appropriately compact.

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 a required undocumented `date` parameter, no usage guidance, and no differentiation from sibling personality/shadow tools, the definition leaves an agent unable to call it confidently.

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 ~67%: fields and precision are documented in the schema, but the required `date` parameter has no description anywhere, and this description does not clarify whether it means a birth date or a query date. The description adds zero parameter meaning beyond 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?

The description names a specific concept ('Shadow card pair, mirror in major arcana of personality card'), but it is jargon-heavy and assumes the caller already knows what a shadow card is. It does not distinguish this from close siblings like astroway_tarot_rider_waite_soul_personality_card or astroway_tarot_rider_waite_birth_card, which likely derive from the same personality-card logic.

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 prerequisites, and no mention of alternatives among the many Rider-Waite siblings. The only context given is a group tag and credit cost.

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