bazi_basic

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

No annotations provided, but the description details inputs like longitude for true solar time and lunar calendar conversion, and lists comprehensive output. It does not mention safety traits but the tool is inherently read-only.

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 concise, with a clear opening sentence and bullet-pointed output list. Every sentence adds value without redundancy.

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 complexity of Bazi and no output schema, the description adequately covers input adjustments and output components. It could mention error handling or validation, but is sufficient for typical use.

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%, and the description adds value by explaining the purpose of gender (for DaYun direction) and longitude (true solar time), which are not fully detailed in the schema descriptions.

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 '计算八字命盘（基础排盘）' and lists all output components, distinguishing it from sibling tools like bazi_dayun and bazi_liunian which focus on specific aspects.

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 this is the primary tool for basic Bazi calculation, but lacks explicit guidance on when to use alternatives or preconditions such as requiring accurate birth time.

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