cn402_zhanbu_qimen

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

No annotations are provided, so the description carries the burden. It discloses a pricing note ('auto-paid in USDC'), which is a behavioral trait. However, it lacks details on error handling, permissions, or side effects beyond computation.

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 front-loaded with many spaced terms and abbreviations, which is messy. It includes a pricing sentence at the end that could be separated. Adequate but not optimally structured.

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 complex divination tool, the description explains the chart type but does not detail the output structure (e.g., what fields are returned). No output schema exists, so more completeness would be beneficial. It's minimally complete.

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 single parameter 'datetime' is fully described in the schema with format and optionality. The description adds explicit format 'YYYY-MM-DD HH:MM' and default behavior, providing meaning beyond the schema.

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 it computes a Qi Men Dun Jia chart (9-palace with stars/doors/gods) for a given datetime, used for strategic decision making. The purpose is clear and distinct from sibling tools like cn402_zhanbu_liuren or cn402_zhanbu_liuyao due to the specific named technique.

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 mentions 'strategic decision making' as a use case, implying when to use this divination method, but lacks explicit guidance on when to prefer this over siblings or any exclusions. No alternative tools are named.

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