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 the useful fact that the result is split into two named components (meridian term, equation of time) and, via the appended metadata, the endpoint and credit cost — but says nothing about latency, auth, or precision behavior.

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 core is two front-loaded sentences: the definition first, then a concrete motivating example. The Kashgar anecdote is illustrative rather than wasteful, and the bracketed metadata is compact, though the prose is slightly evocative for a technical tool.

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 the safety profile. Still, for an 8-parameter computation tool the description does not explain how the two output components are meant to be used or when the tool is the right choice, leaving gaps an agent must fill by inference.

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 50%: the complex parameters (timezone, precision, fields) are already documented in the schema, while date, time, longitude and language rely on regex/range only. The description adds only that the longitude is the birth longitude, and its 'Required' line merely restates schema-required fields, so it does not meaningfully compensate for the 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?

The description names the specific output — a clock corrected to the sun over the birth longitude, decomposed into the meridian term and the equation of time — and ties it to a concrete consequence (the hour pillar moving). It is clear about what the tool produces, though it never states an explicit action verb and does not distinguish itself from sibling tools such as bazi_hour_pillar or chinese_solar_terms.

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?

Usage is only implied via the Kashgar illustration: it signals that the tool matters for births far from a zone's standard meridian, particularly where the hour pillar is at stake. There is no explicit 'use this when X' or 'prefer Y instead' guidance and no stated prerequisites or ordering relative to bazi tools.

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