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 only the credit cost and the count of output categories, disclosing nothing about what the 9 categories contain, how conditions are judged, or what triggers a bonification versus a maltreatment.

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 text is short and front-loads the substantive clause before the bracketed metadata. But the brevity is under-specification rather than economy: for a 15-parameter tool it omits information an agent genuinely needs.

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. But with 15 parameters, 33% schema coverage, no usage guidance, and no behavioral detail, the definition is far too thin for a tool of this complexity, especially with a same-named sibling in another prefix group.

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 only 33% across 15 parameters, so the description carries a heavy burden — yet it explains none of them. It does not clarify required birth data, the compact 'fields' mode, ayanamsa/zodiac selection, or the timezone vs timezoneOffset interaction, leaving roughly ten parameters 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?

The description names a specific domain output ('Planet conditions per Valens: 9 categories'), which tells an agent this is a Hellenistic bonification/maltreatment analysis rather than a chart or aspect tool. However, it lacks a clear verb and never distinguishes itself from the near-identical sibling astroway_helb_bonifications_maltreatments, so an agent must rely on the name alone to choose between them.

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 when-to-use guidance, no prerequisites, and no mention of when to prefer this over the parallel helb_* or greenbaum variants. The '[Group: Hellenistic: Brennan tradition]' tag gives faint tradition context but stops short of routing guidance.

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