Antiscia (Hellenistic)

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

The annotations already cover the safety profile in full (readOnly, idempotent, non-destructive, closed-world). The description adds useful operational context that the annotations do not: cost of 10 credits (Tier 1), the endpoint, and the four required inputs. It says nothing about what the antiscia computation covers or how it handles sidereal versus tropical input.

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?

There is one substantive sentence, front-loaded, followed by a bracketed metadata block. The structure is efficient and the cost and endpoint lines are useful, but the group and required-field lines repeat information already in the schema.

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 13-parameter, domain-specific Hellenistic calculation with an output schema, this description is thin. It does not cover the sidereal/tropical choice or the meaning of the ayanamsa and house-system options. Since an output schema exists, the return format does not need to be explained, but the input-side gaps remain substantial.

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 23% across 13 parameters, so the description should fill the gap, but it does not. It simply restates the four required fields (date, time, latitude, longitude), which the schema already marks as required, and stays silent on ayanamsa/ayanamsaId, zodiacType, houseSystem, timezoneOffset, and the timezone offset rules.

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 it produces 'solstitial antiscia per Hellenistic conventions', which is a slight expansion of the title 'Antiscia (Hellenistic)' by adding the solstitial qualifier. But it gives no basis for choosing it over the many similar siblings, especially astroway_aspects_antiscia and astroway_hellenistic_greenbaum_contra_antiscia. The description's purpose is essentially a restatement of the name.

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 not to, or what alternatives exist. Given a catalog with a plain antiscia tool and a contra-antiscia tool from the same Greenbaum tradition, omitting that routing information leaves a real gap.

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