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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the cost (10 credits, Tier 1), which is genuinely useful behavioral context beyond the annotations, but says nothing about how the draw behaves or what determines the timing result.

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 text is short and the endpoint/group/cost blocks are well-structured metadata. But the actual purpose line is a three-word fragment that is under-specified rather than genuinely concise, leaving little for an agent to act on.

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-value explanation is not required. Still, for a 6-parameter divination tool with no required fields, the definition omits the usage context, the role of the question/seed inputs, and any distinction from sibling draws, leaving the agent under-informed.

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?

With only 50% schema description coverage, three parameters (seed, question, allowReversed) are undocumented in both schema and description. The description adds no meaning for any parameter, not even the central `question` field that would drive a timing reading, so it fails to compensate for the coverage gap.

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?

"Single timing card" conveys a single-card draw oriented to timing questions, which is marginally more than the title. However it gives no verb, no explanation of what a timing card answers, and no differentiation from close siblings like astroway_tarot_marseille_draw_single or astroway_tarot_rider_waite_timing. The purpose is inferable but vague.

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 description provides no when-to-use guidance, no prerequisites, and no mention of alternatives such as draw_single, clarify, or the Rider-Waite timing sibling. An agent must infer the use case entirely from the name.

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