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. The description adds genuinely useful non-schema context — a 10-credit Tier 1 cost and the Greenbaum tradition grouping — which annotations do not carry. It still says nothing about determinism of the calculation, caching, or what the antiscia are computed relative to.

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 core definition is front-loaded in the first line, and the bracketed group/cost metadata is compact and easy to scan. Every element present earns its place, though the overall length is arguably too thin for a 15-parameter calculation tool.

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?

The output schema exists, so return values need not be explained, but for a complex 15-parameter astronomical calculation with 33% parameter coverage the description is far too sparse. It omits what is being computed, for which chart, how it relates to sibling antiscia tools, and any use context.

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%, well below the 50% threshold, so the description is expected to compensate and does not. With 15 parameters (date, time, latitude, longitude, city, name, cosmogram, zodiacType, houseSystem, ayanamsaId, etc.) and no parameter guidance whatsoever, half-documented fields like zodiacType and houseSystem remain opaque from both schema and description.

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 resource ('Solstitial antiscia') qualified by a tradition ('Hellenistic conventions'), which is more than a tautology. However, it names no verb (compute/return) and offers no differentiation from the many antiscia siblings present, such as astroway_aspects_antiscia, astroway_helg_antiscia_hellenistic, and astroway_hellenistic_greenbaum_contra_antiscia. An agent cannot tell from the text alone how this differs from the near-identical helg variant.

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, when to prefer an alternative, or what prerequisites exist. The 'Greenbaum tradition' group tag hints at a school but does not translate into a selection rule. An agent is left to infer usage entirely from the name.

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