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 useful non-schema context - the cost (10 credits, Tier 1) and the Brennan-tradition grouping - but says nothing about what the computation consumes or produces beyond what the schema and output schema carry.

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?

Three short, front-loaded lines with no filler; the purpose leads and the tradition/cost tags are compact metadata. Slightly terse in a way that leaves gaps, but nothing is wasted.

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?

With an output schema and full annotation coverage, the description need not explain return values, and it correctly signals technique and cost. However, for a technical Hellenistic calculation it omits any indication of when the technique is appropriate or how it relates to the Fortune-based sibling, leaving a real gap.

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 100%, so body/fields/precision are already fully documented in the schema, including the detailed birth-data and compact-mode notes. The description adds no parameter-level meaning, which is the expected baseline when the schema does the heavy lifting.

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 technique (Zodiacal Releasing from the Lot of Spirit) and the domain it addresses (career/action periods), which meaningfully distinguishes it from the sibling zodiacal_releasing_fortune variant. It stops short of explicitly naming that sibling or stating the Spirit-vs-Fortune contrast outright.

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 when-to-use guidance, no prerequisites, and no alternatives are named despite several closely related siblings (zodiacal_releasing_fortune, zr_peak_periods, zr_loosing_of_bond). The agent is left to infer selection purely from the technique name.

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