Zi Wei Dou Shu Chart

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

The readOnlyHint already signals a safe calculation, and the description adds meaningful behavior: results are reproducible, server current time is not read, and arbitrary settings cannot bypass the 安星码 requirement. It stops short of describing error behavior or validation failures for invalid codes or incomplete time data.

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 definition is compact and front-loads the purpose, required inputs, and key restrictions in one dense sentence. It wastes little space, though the compression leaves important parameter semantics unaddressed.

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 calculation tool with 27 parameters, 14 required fields, no schema descriptions, and no output schema, this description is not complete enough for reliable invocation. It gives useful high-level constraints but omits how to populate most parameters and what the returned chart data looks like.

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 0% across 27 parameters, so the description must carry the burden. It only groups a few concepts—birth moment, 安星码, target civil time and source—while leaving key parameters such as is_male, calendar_type, use_true_time, timezone fields, DST handling, and longitude/latitude vs city_name unexplained.

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 states a specific verb (计算) and resource (三合紫微主盘), plus the exact derived periods: 大限、流年、流月、流日、流时. The term 三合紫微 distinguishes it from sibling chart tools such as qimen, qizheng, vedic, and bazi calculate_chart tools.

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?

It establishes prerequisites clearly: a complete birth moment, a valid 安星码, and an explicit target civil time plus its source. It also states exclusions—no server current time and no bypassing the 安星码 with arbitrary settings—though it does not explicitly route the agent to alternative chart tools.

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