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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely useful operational context absent from annotations: the cost tier (10 credits) and the endpoint/group membership. It does not explain computation behavior or how the periods are derived, but the annotation bar is met.

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 in a single clause, followed by bracketed metadata (group, endpoint, cost) that is compact and scannable. Nothing is wasted, though the body is arguably too thin to be ideal for a tool in such a crowded namespace.

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-format explanation is not required, and the input schema is comprehensive. The gaps are around disambiguation from the many ZR siblings and any sense of what the result is used for, which leaves the definition merely adequate for a specialized computation 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 100% and the birth-data schema is extremely well documented (formats, tz handling, houseSystem letters, rejection of short forms). The description adds no parameter-level information, so the baseline 3 for fully-covered schemas is correct.

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 technique (Zodiacal Releasing) and its source point (Lot of Fortune), and adds the derived subject matter ('body/livelihood periods'), which is enough to distinguish it conceptually from the Spirit-based sibling. However, it never names the near-duplicate siblings (e.g. astroway_helb_zodiacal_releasing_fortune, astroway_hellenistic_brennan_zodiacal_releasing_spirit), so an agent cannot separate the Brennan variant from the helb variant on the description alone.

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 statement of when to use this tool versus the Spirit variant, the peak-periods sibling, or the helb duplicate. The description gives no context on what question the output answers or what prerequisites apply. Only the technique name implies usage.

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