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

Annotations already declare a safe, idempotent, closed-world read, and the description does not contradict them. It adds the genuine prerequisite that a birth time is needed, plus the credit cost, but says nothing about what the response contains or what happens if time is omitted (the schema marks only date as required).

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 compact sentences, with the core definition front-loaded and the prerequisite second. The group and cost tags are boilerplate metadata but short and informative; nothing is 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?

Return values need not be explained since an output schema exists, and the prerequisite is stated. For a domain with four near-identically named zodiac siblings, though, the definition leaves the agent without enough to reliably pick this tool over inner_animal.

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 only 50% schema description coverage across 8 parameters, the description's 'requires birth time' usefully elevates the `time` parameter beyond its optional schema status. However, it adds nothing about date format, timezone/timezoneOffset interaction, or the compact-mode fields, leaving half the surface 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 resource and scope: the hour-of-birth branch animal, with a plain-language gloss ('represents the deepest self'). That distinguishes it from the year-based astroway_chinese_zodiac_animal, but it never names the closest sibling, astroway_chinese_zodiac_inner_animal, which an agent could easily confuse it with.

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?

'Requires birth time' is a real prerequisite, which is more than most sibling definitions offer. It still gives no when-to-use or when-not-to-use guidance relative to zodiac_animal, inner_animal, or zodiac_element, so selection relies on the name alone.

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