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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine methodological context beyond the annotations: the month is counted like any other branch, the three criteria are reported unweighted, and the cut points are this API's own convention. That limitation disclosure is exactly the kind of behavior an agent needs, though auth/rate-limit details are absent (credit cost is given in the metadata block).

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 sentences are front-loaded with the core concept, and the caveat sentence names both limits economically. The prose is dense jargon ("support-and-suppress", "weighted hidden-stem count") which reduces immediate readability, but nothing is wasted or padded.

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 explained, and annotations cover safety. What remains missing is any positioning against the large BaZi sibling set and any description of the many input parameters, which a tool with 11 options arguably needs. The methodology and cut-point caveats partially fill the gap, making this minimally adequate.

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?

With 11 parameters and only 36% schema description coverage, the description is expected to compensate, but it mentions no input parameters at all. Nothing is said about date/time handling, timezone vs timezoneOffset, stageSchool, precision, fields or includeFullTable, so the coverage gap is unaddressed.

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 names a specific computation: the day-master support-and-suppress reading over the weighted hidden-stem count, with the three classical criteria (season, root, allies) and the favourable elements. This is a concrete verb-plus-resource statement rather than a tautology. It does not, however, explicitly distinguish itself from close siblings such as astroway_bazi_day_master, astroway_bazi_hidden_stems or astroway_bazi_element_balance, leaving the agent to infer the boundary.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance. The description explains what is computed but not the conditions under which an agent should pick this over the many adjacent BaZi endpoints (e.g. day_master, element_balance). No prerequisites or sequencing are stated.

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