Lenormand: Single Card

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds genuinely useful context: the concrete endpoint, the single required input, and a cost caveat noting the endpoint is absent from the public credit manifest — an agent can plan around pricing uncertainty.

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 core purpose is front-loaded in one sentence and the bracketed lines are compact. The metadata block (group, endpoint, required, cost) is template-like but each line carries operational value, so little 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?

For a one-parameter lookup with a full output schema and complete annotations, the description supplies what's missing operationally: endpoint, input requirement, and cost caveat. The only real gap is not pointing to the sibling listing tool as the way to obtain valid slugs.

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 100% and the schema itself documents the slug format ('lowercase and hyphenated'), so semantics are already carried. The description's '[Required: slug]' only repeats the required list and adds no format, example, or slug-discovery hint beyond the schema; 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?

States a specific verb and resource with explicit scope: 'Single Lenormand card lookup by slug.' The word 'Single' distinguishes it from the sibling list endpoint astroway_tarot_lenormand_cards, and the endpoint line confirms it is a single-resource fetch.

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 word 'Single' implies this is the per-card detail lookup rather than a listing, but no when-to-use guidance is stated and no sibling is named. An agent must infer that astroway_tarot_lenormand_cards should be called first to discover valid slugs.

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