cn402_bazi_full

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

No annotations are provided, so the description bears full responsibility. It mentions it's comprehensive but gives no behavioral details such as whether it's a read operation, what the response format is, any authentication requirements, 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 is somewhat verbose with repetitive phrasing ('complete BaZi reading / full Chinese astrology…') and includes a pricing note that seems tangential. It front-loads the purpose but could be more concise.

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 a full BaZi reading and the absence of an output schema, the description should explain what the output contains and how to interpret it. It lists components but lacks details on format or structure.

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%, so baseline is 3. The description does not add meaning beyond what the schema already provides for the datetime and gender parameters.

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 it is a 'complete BaZi reading' and 'single comprehensive endpoint combining all BaZi analyses', explicitly distinguishing it from the many specialized sibling tools like cn402_bazi_sizhu or cn402_bazi_wuxing.

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 usage for a full BaZi reading, but does not explicitly state when to use this tool versus the individual BaZi components or when not to use it. Alternatives are only implied by the sibling list.

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