cn402_iching_hexagram

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

No annotations are provided, so the description must convey behavioral traits. It mentions 'Price: unknown on Base (auto-paid in USDC)', which adds context about cost. However, it does not disclose what 'full traditional interpretation' includes (e.g., judgment, image, lines) or whether the operation is read-only, making the behavior somewhat opaque.

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 description is overloaded with keywords and translations (e.g., 'I Ching hexagram lookup / 卦象查询 / 64 hexagrams reference / ...') that are not concise and do not add clarity for an AI agent. The actual functional sentence is solid, but the extra fluff harms conciseness. The pricing line is also non-essential.

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 should detail what the output includes, but it only says 'full traditional interpretation', which is vague. It does not mention structure (e.g., name, judgment, image, lines) or format. Given many sibling tools, more specifics are needed for an agent to correctly interpret results.

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?

The input schema has 100% coverage with the parameter 'number' described as 'Hexagram number 1-64 (required)'. The description adds that it is a lookup by number and yields a full interpretation, but does not enhance parameter meaning beyond the schema. Baseline 3 applies since schema already covers the parameter.

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 clearly states the tool's purpose: 'Look up a specific I Ching hexagram by number (1-64) and get its full traditional interpretation.' The verb 'look up' and resource 'I Ching hexagram' are specific, and it distinguishes from siblings like cn402_iching_list (list all) or cn402_iching_divine (random divination).

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 implies that the tool is used when you have a specific hexagram number, but it does not provide explicit guidance on when to use this versus alternatives such as cn402_iching_divine or cn402_iching_full. No when-not-to-use or alternative tool suggestions are given.

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