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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered without description help. The description adds the cost ('10 credits (Tier 1)') and a taxonomy group, which are useful behavioral/metering details not present in the structured fields. It does not describe the payload or return shape, though an output schema exists.

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 prose is extremely tight and front-loads the resource identity, with cost and group following as compact bracket tags. Nothing is redundant or bloated, though the brevity edges into under-specification rather than pure conciseness.

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?

Given a fully documented two-parameter schema, an output schema, and rich read-only annotations, the definition has enough structure to be callable. The main missing context is usage routing among the many Lenormand/Tarot siblings, which leaves an agent to infer when this reference listing is preferable to a draw 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 description coverage is 100%, so both 'fields' and 'precision' are fully explained in the input schema, including the dotted-path syntax and rounding semantics. The description adds no parameter meaning beyond that, so the baseline 3 is appropriate.

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 identifies the resource as a 36-card Lenormand oracle deck but never supplies a verb or action, leaving it to implication that the tool returns the full card list. It does not differentiate this reference listing from siblings such as astroway_tarot_lenormand_cards_slug or the various draw_* spread tools. The title 'Lenormand: All Cards' carries much of the disambiguation that the description itself lacks.

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 the many sibling tools (draw_three_card, draw_grand_tableau, cards_slug, houses) that an agent could confuse with this one. The closest thing to context is the group tag '[Group: Tarot: Lenormand]', which categorizes rather than routes.

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