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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description usefully adds the cost (10 credits, Tier 1) and the endpoint, but says nothing about the nature of the nine categories or any rate/usage constraints beyond cost.

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?

Front-loads the one-line purpose and then packs group, endpoint, required params, cost, and alias into tight bracketed lines. Efficient; the redundancy of restating the four required params is the only minor waste.

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 no explanation, and the alias/endpoint/cost framing is complete for an alias tool. However, with 15 params at 33% schema coverage and a domain term ('9 categories') left unexplained, the description is only marginally adequate for correct invocation.

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 coverage is only 33% across 15 parameters, so the description carries the burden of compensating — but it merely repeats the four required params (date, time, latitude, longitude) already listed in the schema and says nothing about the ayanamsa, timezone, houseSystem, fields, precision, or zodiacType options.

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 the resource and scope ('Planet conditions per Valens: 9 categories') and explicitly identifies itself as a Cursor-friendly alias for the canonical `astroway_hellenistic_brennan_bonifications_maltreatments`, which helps distinguish it from the many HB siblings. The intent is somewhat jargon-dependent ('bonifications/maltreatments'), but an agent can place it in the Hellenistic/Brennan family.

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?

The required inputs, endpoint, and credit cost are given, and the alias relationship implies when it is interchangeable with the canonical tool. There is no explicit when-to-use-vs-alternatives guidance against the other Brennan/Hellenistic tools (e.g. joys_of_planets, lots_15).

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