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

Annotations already declare the safe read-only, idempotent, non-destructive profile, so the bar is low. The description adds genuinely useful context: the 10-credit Tier 1 cost and the note that it is a cursor-friendly alias of astroway_hellenistic_greenbaum_quality_of_time, which signals duplication. No auth or rate-limit details.

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?

Dense and front-loaded: one purpose line followed by compact bracketed tags for group, endpoint, required inputs, and cost. Little waste, though the opening line carries almost no functional information.

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 15-parameter tool with 33% schema coverage, the description omits guidance on the optional configuration params that distinguish Hellenistic variants. An output schema exists, so return values are excused, but the input-side complexity is largely unaddressed.

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% (15 params), so the description must compensate, but it merely repeats the four required params already marked required in the schema. Nothing is added about the eleven optional params (houseSystem, zodiacType, ayanamsa, fields, precision, timezone), which materially affect a Hellenistic calculation.

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?

"Synchronistic quality of a moment" is close to a restatement of the name/title and does not say what the tool actually computes. However, the bracketed metadata names the tradition (Hellenistic: Greenbaum) and endpoint, which does differentiate it from the Brennan/Schmidt/Hand siblings in the same family.

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?

No when-to-use or when-not-to-use guidance, and no named alternatives (e.g., vs. astroway_hellenistic_brennan_quality_of_time or other timing tools). The cost tag is the only decision-relevant hint provided.

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