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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that — a specific cost (10 credits, Tier 1) and the endpoint — but says nothing about pagination, response shape, or what the five positions represent.

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 purpose is front-loaded in the first line, and the remaining lines are short tagged metadata rather than prose. The alias note is somewhat redundant with the tool name, but nothing is verbose or buried.

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, and annotations carry the safety profile. However, three of six parameters are undocumented and the description never explains what the '5-card spiritual development spread' positions or options are, leaving gaps for a 6-parameter tool.

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 50%: art, fields, and precision are documented in the schema, while seed, question, and allowReversed are undocumented in both places. The description adds no parameter meaning at all, so it fails to compensate for the uncovered half.

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 first line states a specific resource — a 5-card spiritual development spread — which distinguishes it from sibling draws like draw_chakra or draw_shadow_work. The verb (draw) is implied rather than stated, and the definition leans on the metadata block instead of the action itself.

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 or when-not-to-use guidance. The note that it is a 'cursor-friendly alias' for astroway_tarot_rider_waite_draw_spiritual_path is genuinely useful for routing, but no condition is given for choosing this spiritual-path spread over the chakra, shadow-work, or relationship spreads.

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