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

No annotations are provided, so the description carries the full disclosure burden. It does useful work: it lists the returned fields (essence, judgment, image, love/career readings, guidance, six line texts) and discloses the ambiguous-input fallback (returns candidates rather than failing). It doesn't mention pagination, error behavior for out-of-range numbers, or an explicit read-only statement, so not a 5.

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?

Two sentences, front-loaded with the lookup action and followed by the return contents. Dense but nearly every clause carries information. The long parenthetical enumerations make it slightly heavy, but there is no filler.

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?

With no output schema, the description usefully enumerates the return payload, and the language parameter is thoroughly documented in the schema. The only gap is the lines parameter (highlighting changing lines), which is a functional behavior the description never mentions, so an agent might overlook 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?

Schema coverage is 100%, so the baseline is 3. The description adds genuine meaning beyond the schema: it documents the Chinese-character input form (旅) that the schema's parameter description omits, gives a concrete English-name example, and explains the ambiguity behavior for pinyin, which the schema does not.

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 ("Look up") and resource ("one of the 64 I Ching hexagrams") and enumerates the accepted identifier forms, which is clear and actionable. It doesn't explicitly differentiate itself from the sibling cast_i_ching (the casting tool) or get_tarot_card_meaning, so it stops short of 5.

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 context is implied: this is the lookup tool for retrieving a known hexagram's meaning. The description clarifies that ambiguous pinyin returns candidates, which helps the agent handle fuzzy input. However, it never states when to use this versus cast_i_ching (to generate a hexagram) or get_tarot_card_meaning, leaving the sibling routing to inference.

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