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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds operational context the annotations do not: the 10-credit Tier 1 cost and the BaZi group membership. It adds no pagination, caching, or dependency behavior, so it earns a moderate rather than high score.

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 short, front-loaded with what the tool returns, and every element (including the group and credit tags) carries information. Slightly clipped on the phrasing of the second sentence but free of padding.

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 no prose, and the safety profile is in annotations. What is missing is workflow context: whether time is needed for a day-master-only reading, where this fits relative to four_pillars or ten_gods, and any preconditions on the date input. Adequate but with clear gaps for a 7-parameter chart tool.

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 57%, and the two central parameters (date, required, and time) carry only regex patterns with no descriptions in either the schema or the description. The description explains nothing about how the date/time inputs drive the day master or how fields/precision/language behave, so it fails to compensate for the coverage gap.

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 output: day stem element, yin/yang polarity, and canonical archetype description, and situates it in BaZi as the 'self' character. It is distinguishable from siblings like four_pillars or year_pillar, though it never names a contrasting sibling explicitly. Clear verb+resource, one notch below full sibling differentiation.

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 explicit when-to-use or when-not guidance, and no alternative tool is named, despite the dense BaZi sibling cluster (four_pillars, hidden_stems, ten_gods, strength). The reader can infer this is one sub-step of BaZi analysis, but nothing routes them to or away from it.

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