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 covered structurally. The description does add genuinely useful behavior not in annotations - the 10-credit Tier 1 cost - but says nothing about what the 'conditions analysis' returns or any computation caveats.

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?

Two short lines with the purpose front-loaded and no filler prose. The bracketed group/cost tags are structural boilerplate, but the cost tag carries real information, so the brevity is defensible even though it is brevity by omission rather than precision.

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?

For a 15-parameter chart computation, the description omits the required date/time/latitude/longitude inputs, offers no hint of the conditions-analysis output, and fails to disambiguate from its helg-prefixed twin. An existing output schema covers return-value explanation, but the remaining gaps are too large for a tool of this complexity.

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 schema leaves most inputs undocumented (e.g. city, name, cosmogram, zodiacType, houseSystem have no descriptions). The description adds nothing about any parameter, failing to compensate for the coverage gap.

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 says the tool computes the Lot of Eros plus a 'conditions analysis,' which is more than the bare title but still vague about what those conditions are and what the output represents. It gives no differentiation from the near-identical sibling astroway_helg_lot_of_eros_detail, so an agent cannot confidently choose between the two from the text 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 when-to-use guidance, no prerequisites, and no named alternative, despite a duplicate 'lot_of_eros_detail' tool existing under the helg prefix. The only context offered is a tradition group tag, which does not tell the agent when this tool is the right pick.

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