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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world behavior, so the safety profile is covered. The description adds genuinely useful non-annotation facts: the exact endpoint and a 10-credit cost. It does not disclose the response shape, but an output schema exists so that burden is reduced.

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?

One-line summary followed by dense, front-loaded bracket metadata; nothing is wasted. The format is terse and scannable, though the summary line itself is quite thin.

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?

With an output schema present and annotations covering safety, the description need not explain return values, and it does note cost and endpoint. Still, for a 15-parameter calculation tool with three enums and low schema coverage, it leaves the optional parameters and the distinction from sibling antiscia tools unexplained.

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 needs to compensate. Instead it merely repeats the four required parameters already declared in the schema and adds nothing about the eleven optional ones (houseSystem, zodiacType, fields, precision, ayanamsa, etc.). It adds no semantic value beyond structured data.

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 astrological technique (solstitial antiscia) within a named tradition (Hellenistic/Greenbaum), which is more specific than a tautology. However, it supplies no verb describing what is computed or returned, and it does not distinguish itself from near-identical siblings such as astroway_helg_antiscia_hellenistic or astroway_aspects_antiscia. Purpose is identifiable but underspecified.

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 versus the many antiscia-related siblings (astroway_aspects_antiscia, astroway_helg_antiscia_hellenistic, astroway_hellenistic_greenbaum_contra_antiscia). The bracket metadata gives operational facts (required params, cost, endpoint) but nothing about selection criteria.

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