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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds genuinely useful operational context: a 10-credit Tier 1 cost and the Schmidt-tradition grouping. It does not, however, add anything about auth, rate limits, or result behavior beyond the cost line.

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?

Compact and front-loaded with no filler, but the single substantive line is too thin for a 15-parameter chart tool. The metadata markers (group, cost, alias) are well structured and earn their place.

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?

The tool is complex (15 params, 3 enums, low schema coverage) and the description does not address what the analysis returns or which inputs drive it, even though an output schema exists to cover return shape. For this level of complexity the description is materially incomplete beyond the cost and alias hints.

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, four of them required (date, time, latitude, longitude), yet the description supplies zero parameter meaning. It does not compensate for the uncovered fields or clarify the interaction between timezone, timezoneOffset, and ayanamsa that the schema only partially documents.

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 body text "Qualitative + quantitative analysis" essentially restates the tool name/title, leaving the actual Hellenistic Schmidt doctrine unnamed and unexplained. The only genuine disambiguation is the note that this is a cursor-friendly alias for `astroway_hellenistic_schmidt_qualities_and_quantities`, which helps identify the twin but not the 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 statement of when to use this tool, what question it answers, or what to use instead. The alias note implies interchangeability with the canonical tool, but no condition selecting either over the wide set of `hels_*` / `hellenistic_schmidt_*` siblings is given.

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