cn402_iching_bagua

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

With no annotations provided, the description carries the full burden but only mentions pricing ('Price: unknown on Base (auto-paid in USDC)'), which is about cost, not behavioral traits. It does not disclose side effects, authentication needs, or rate limits.

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 contains verbose and repetitive elements (multiple translations and synonyms) before the core sentence. The pricing line is irrelevant for tool invocation. The key information is buried.

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 simple listing tool, the description covers what data is returned (trigrams with mappings). However, it lacks detail on output format and default behavior (both pre- and post-Heaven). Without an output schema, more context on returned structure would improve completeness.

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 for the one parameter 'type' with description 'preHeaven | postHeaven (optional, default both)'. The description adds minimal value beyond repeating 'Pre-Heaven Post-Heaven' in the title, so 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?

The description explicitly states 'Get all 8 trigrams (Ba Gua) with element, direction, family role, body part, and natural symbol mappings,' which clearly identifies the tool's purpose. It distinguishes from siblings like iching_coin or iching_divine by focusing on retrieving trigram mappings.

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 guidance on when to use this tool versus other I Ching tools (e.g., iching_hexagram, iching_yao) or when to choose preHeaven vs postHeaven. No usage context or alternatives are mentioned.

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