getBaziChart

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

With no annotations, the description carries the full behavioral burden. It frames the tool as a computation and lists what is returned, which conveys read-only, non-mutating behavior, but says nothing about permission needs, latency, or whether historical/future dates are restricted or error out.

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?

Front-loaded: the verb and resource come first, the output enumeration second. The bilingual duplication of the same sentence adds length without new information, but there is no filler beyond that.

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?

There is no output schema, so listing the returned fields (Ten Gods, Hidden Stems, Decade Fortune) is genuinely useful compensation and tells the agent what to surface. The remaining gap is input-side: it never clarifies which datetime field to supply or why gender is required.

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 description coverage is 100% and every parameter carries its own bilingual description, so the schema does the heavy lifting. The description adds no extra meaning — it does not explain the required gender field, the lunar-vs-solar choice, or the eightCharProviderSect default.

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?

States a specific verb and resource ('Calculate a complete BaZi chart') and enumerates the outputs (eight characters, Five Elements, Ten Gods, Hidden Stems, Decade Fortune). Nothing about it overlaps with findBirthDates, getAlmanac, or calculateBoneWeight, so an agent can discriminate it without opening the schema.

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 phrase 'from birth datetime' implies the input context but never states when to prefer this over the sibling fortune/almanac tools, nor how to choose between lunarDatetime and solarDatetime — a central decision for this tool. Usage is only inferable, not stated.

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