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

With no annotations, the description carries the full burden and does substantial work: it enumerates the returned artifacts (King Wen number, Chinese name, Unicode symbol, judgment, translation, plain-language meaning, moving lines, transformed hexagram). It does not mention the inherently non-deterministic/random nature of the cast, which is the one notable behavioral gap.

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?

A single front-loaded paragraph that leads with the action and method before enumerating outputs; every clause maps to a distinct returned element. Slightly dense listing of return fields but no filler sentences.

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?

No output schema exists, so the description must describe returns — and it does so thoroughly, covering primary hexagram, judgment/translation, moving lines, and transformed hexagram. For a zero-required-param generative tool, an agent has everything needed to call and interpret it.

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?

Only one parameter with 100% schema coverage, so the schema already documents it fully, including the 'echoed back for context' behavior. The description's note that the question can be optionally attached adds little beyond the schema, so baseline 3 applies.

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 ('cast') and resource ('I Ching (Yijing) hexagram') and names the method ('classic three-coin method'), making it immediately clear this generates a new reading rather than looking up a known one. That generation semantics inherently distinguishes it from the get_hexagram and list_hexagrams siblings.

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?

Usage is only implied: 'cast' signals a fresh randomized divination, which contrasts with the lookup/list siblings, but the description never states when to choose this over get_hexagram or list_hexagrams, nor any prerequisites. The optional question guidance is the only explicit usage instruction.

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