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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description usefully adds operational context the annotations do not carry — the 10-credit cost and the required input set — but says nothing about authentication, output shape, or what the "9 categories" actually contain. With annotations doing the heavy lifting, this is an adequate 3.

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 statement is front-loaded and free of filler, and the bracketed metadata is compact. However, the terse phrasing tips into under-specification: the description is short because it omits information, not because it is economical.

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 for a 15-parameter tool with weak schema coverage the description should do far more. It gives no usage context, no disambiguation from the sibling helb_bonifications_maltreatments, and no explanation of the nine categories, leaving an agent under-informed for a non-trivial chart calculation.

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 real burden — but it merely restates the four required parameters, which are already listed in the schema's required array, and adds no semantic meaning. Undocumented parameters such as cosmogram, zodiacType, and ayanamsaId receive no clarification here, so the coverage gap is left unfilled.

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 gives a bare statement of what is computed ("Planet conditions per Valens: 9 categories"), which is enough to recognize the Hellenistic bonification/maltreatment concept but not a specific verb+resource framing. It does not distinguish itself from near-identical siblings such as astroway_helb_bonifications_maltreatments or astroway_dignities_essential_dignities, leaving the agent to guess which variant to pick.

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, when-not-to-use, or alternative-tool guidance anywhere in the description. The only routing-like content is a group tag and endpoint path, which tell the agent where the tool lives but not when to choose it over the highly similar helb_ and hand_ Hellenistic tools.

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