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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context the annotations lack: the credit cost (10 credits, Tier 1) and the spread size. It says nothing about how seed/question affect the draw or what the returned cards look like, so it stops short of full behavioral disclosure.

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?

Two short bracketed fragments plus one sentence — nothing bloated and the spread type is front-loaded. It is terse rather than padded, though the bracket metadata is presentation scaffolding rather than agent-facing guidance.

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 for a 5-parameter tool at 40% schema coverage with no usage guidance and no parameter semantics, the definition is too thin. It informs the agent of cost and spread size but not when or how to invoke it correctly.

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 40% and the description mentions none of the five parameters. Critical semantics such as what 'seed' controls, how 'question' influences the reading, or what 'allowReversed' defaults to are left entirely to the schema, which itself documents only 'fields' and 'precision'. With more than half the parameters undocumented, the description fails to compensate.

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 the artifact produced ('6-card shadow integration spread'), which is more than a restatement of the tool name and distinguishes it from sibling tarot spreads like love triangle or career. However, it never states the act (draw/randomize) nor the mechanism, leaving the agent to infer that this is a draw operation from the tool name alone.

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 mention of prerequisites, and no reference to alternatives such as astroway_tarot_rider_waite_draw_spiritual_path or astroway_tarot_rider_waite_shadow_card. The spread name implies a thematic context but nothing is stated explicitly.

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