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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description usefully adds cost (10 credits, Tier 1), the HTTP endpoint, and the fact that this is an alias of astroway_hellenistic_schmidt_morning_evening_stars — real behavioral context. It says nothing about what is computed or returned, but with annotations carrying the safety burden this is acceptable.

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?

Purpose is front-loaded, then bracketed metadata lines that are each scannable and factual, ending with the alias note. Nothing is padded, though the metadata block is somewhat dense relative to the single line of actual explanation.

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, and annotations cover safety. However, for a 15-parameter tool at 33% schema coverage, the description omits any guidance on the astrological configuration knobs (ayanamsa, zodiacType, houseSystem) or the meaning of the classification result, leaving it minimally adequate.

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 is expected to compensate — but it only restates the four required fields already declared in the schema's required array. It adds no meaning for the required date/time/lat/long inputs and ignores undocumented optional parameters such as city, name, cosmogram, zodiacType, and houseSystem.

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 opening line states a specific operation on a specific resource: classifying planets/stars as morning vs evening stars. The group tag '[Group: Hellenistic: Schmidt tradition]' and endpoint path differentiate it from the parallel Brennan/Greenbaum/Hand traditions in the sibling list. It stops short of explaining what the classification output means, but the purpose is clear enough to route correctly.

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 mention of alternatives such as astroway_hels_stations_and_phases or the non-alias form of this same tool. The required-parameter list and cost note are operational facts, not usage guidance.

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