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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful semantic content (what relations are computed) and a cost tag (10 credits, Tier 1), but says nothing about auth, limits, or how natal time/zone defaults affect results. Adequate but not rich beyond the annotations.

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?

Two tight sentences with the operation front-loaded before the return contents, plus compact group/cost metadata. No padding or repetition, though the enumerated return fields partly duplicate what the output schema already provides.

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?

An output schema exists, so return values need not be re-explained, and the safety profile is carried by annotations. However, for a 7-parameter tool with low schema coverage, the missing parameter documentation and absence of any sibling routing leave real gaps an agent must guess around.

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 only 29% (fields and precision only), so the description must compensate — and it does not. It never mentions natalDate, targetYear, natalTime, natalTzOffset, or language, leaving the two required parameters and the timezone input undocumented in both places.

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 operation (compares target year pillar against natal day master and natal year branch) and enumerates the analytical outputs (Sheng-Ke element-flow relation, 六冲 branch clashes, 三合 trine support). Clear verb+resource, but it never distinguishes itself from close siblings such as astroway_bazi_year_pillar, astroway_bazi_year_pillar_decade, or astroway_bazi_monthly, so an agent cannot route between them from the text alone.

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?

No when-to-use statement, no when-not-to-use, and no named alternative despite a dense BaZi sibling cluster. The only scoping hint is implicit in the phrase 'target year pillar', which an agent must infer means an annual forecast use case.

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