bazi_cast

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It explicitly warns the host not to invent pillars, stems, branches, or wuxing, and it discloses the lunar-python dependency. This is valuable behavioral context beyond the schema, though it does not cover failure behavior or default timezone handling.

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 two sentences, front-loaded with the action and resource, and every sentence adds meaningful information. There is no redundancy or filler.

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?

With a full output schema and 100% parameter coverage, the description sufficiently covers the tool's purpose and key constraints. A minor gap is that it does not clarify the default timezone behavior when the optional timezone parameter is omitted, but this is not critical given the schema details.

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%, so the description need not elaborate on parameters. The mention of 'Gregorian birth datetime' aligns with the required datetime parameter but adds no meaning beyond what the schema already provides. 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 uses the specific verb 'Cast' and clearly identifies the resource as a 'Bazi (八字 / Four Pillars) chart' with input 'from a Gregorian birth datetime'. This unambiguously distinguishes it from sibling tools like iching_cast and xiaoliuren_cast.

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 clearly states the use case: casting a Bazi chart from a Gregorian birth datetime. It does not explicitly name alternatives or exclusion criteria, but the context is clear enough that an agent can determine when to use it versus other casting tools.

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