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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only the credit cost (10 credits, Tier 1), which is mildly useful operational context but says nothing about what the classification depends on (heliacal visibility, phasis, rising/setting relative to the Sun) or how results are shaped.

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 text is tight and front-loaded, with the core statement in the first line and metadata bracketed below. There is no padding, but the extreme brevity is under-specification rather than economy 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?

An output schema exists, so return values need not be described, but the tool still requires 4 positional inputs and exposes 15 parameters with heavy astronomical/terminology semantics that the description never touches. For a specialist Hellenistic timing calculation, the description is too thin to let an agent invoke it confidently.

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 coverage is only 33% across 15 parameters, so the description is expected to compensate and does not: it mentions no parameter at all. Undocumented fields (city, name, cosmogram, ayanamsaId, zodiacType, houseSystem) receive no explanation in either the schema or the description, leaving the agent to guess the effect of these inputs on the classification.

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 phrase 'Morning vs evening star classification' names the resource (morning/evening stars) and implies a classifying action, so the general topic is recoverable. However, it gives no verb like 'compute/determine for a chart', no scope statement, and does not distinguish this tool from the near-identical sibling astroway_hels_morning_evening_stars. It reads as an expansion of the title rather than a self-contained purpose.

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 the competing sibling (astroway_hels_morning_evening_stars) or of how the Schmidt-tradition output differs from that one. The only context is a group tag and credit cost, which does not tell an agent when to select this tool.

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