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

With readOnlyHint/idempotentHint/destructiveHint already covering the safety profile, the description's useful addition is the cost disclosure (10 credits, Tier 1) and the group membership. It says nothing about what the computation actually produces or any input constraints beyond the schema, so it adds modest value over annotations.

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?

Very compact and front-loaded: the core statement comes first, followed by clearly delimited bracket metadata tags. The alias parenthetical is worth its space for disambiguation. Nothing extraneous.

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 not be explained. Still, for a 15-parameter specialist tool with heavy sibling overlap and 33% schema coverage, the description does not give enough to guarantee correct invocation — chiefly which antiscia variant to pick and how the required inputs should be formed.

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, and the four required inputs (date, time, latitude, longitude) have no descriptions anywhere. The description supplies no parameter meaning at all, so it fails 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?

States a specific resource ('antiscia') qualified by 'solstitial' and 'Hellenistic conventions', which is more than a tautology of the title. It does not, however, distinguish itself from the neighboring astroway_aspects_antiscia or astroway_helg_contra_antiscia tools, so an agent still has to guess which antiscia variant applies.

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 alias note ('Cursor-friendly alias for ...') is genuine routing guidance — it tells the agent which of two equivalent tools to prefer in a Cursor context. But there is no when-to-use/when-not guidance against the other antiscia siblings (aspects_antiscia, contra_antiscia), so usage remains implicit.

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