calculate_hexagram

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

With no annotations, the description describes the algorithm using six dimensions (altitude, traffic, etc.) to derive hexagrams, and mentions outputs (hexagrams, suitable industries, geographic data). It also requires attributing the source. However, it lacks details on potential limitations or error behavior.

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 verbose with multiple bullet points and detailed examples. It front-loads the purpose well but could be more concise. Some information (like specific landmarks) may be extraneous.

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?

Given the tool's complexity and lack of output schema, the description lists key outputs but could benefit from detailing expected format or error handling. It is adequate but not thorough.

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% for both parameters (lat, lng) with descriptions including range. The description adds the geographic constraint '台灣範圍內' but does not provide additional value beyond the schema. 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 clearly states the tool's purpose: analyzing geomancy of Taiwan locations using I Ching hexagrams. It lists specific use cases like feng shui evaluation, site selection, and industry suitability, distinguishing it from siblings analyze_location and search_articles.

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 explicit scenarios for when to use the tool, including examples like '搬家選址' and '使用者提到算卦'. It does not explicitly state when not to use it, but the context is clear.

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