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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely useful behavioral context beyond that: the `balance` object opens branches and counts three ways, and the top-level elementCounts/dominantElement/missingElements are deprecated but keep their legacy (four-character) semantics until 2027-09. This is exactly the kind of output-contract disclosure that helps an agent interpret results.

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?

Purpose is front-loaded and the deprecation caveat is placed after it, which is the right ordering. But the text is dense with internal jargon ('opens the branches', 'stays at eight') and appears truncated mid-sentence at '2027-09…', which weakens the structure.

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 restated, and the deprecation note usefully covers the output contract. What is missing for a tool of this complexity is any parameter guidance and any differentiation from the many sibling BaZi tools, leaving gaps the 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?

Eleven parameters at only 36% schema description coverage, and the description says nothing about any of them – not date/time, not timezone vs timezoneOffset, not fields compact mode. With coverage this low the description is expected to compensate for the undocumented parameters and does not.

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 opening sentence names a specific resource (element balance across the whole chart) and the following sentences specify the computation precisely: three counting methods over all eight characters. However, it never distinguishes itself from close siblings such as astroway_bazi_hidden_stems or astroway_bazi_strength, which also operate on the same chart, so the agent gets no routing signal.

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 or when-not-to-use guidance, and no alternative tool is named. The only conditional information is about deprecated output fields, which affects interpretation of the response, not tool selection.

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