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 adds a genuinely useful non-annotation fact — the 10-credit Tier 1 cost — but says nothing about what the operation computes or how the result is 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?

It is short, but the brevity comes from under-specification rather than economy. The bracketed metadata lines are structurally front-loaded, yet the one substantive sentence conveys almost nothing.

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, and the 15-param surface is largely conventional chart input. Still, a niche Hellenistic classification tool with no explanation of what it produces or when to invoke it leaves an agent unable to call it with confidence.

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%, so the description is expected to compensate, and it supplies zero parameter information. The four required params (date, time, latitude, longitude) are self-explanatory from their names, which keeps this above a 1, but most of the 15 params get no added meaning.

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?

"Nine fates classification" is essentially a gloss of the tool's own name (Ennea Mooirai = nine fates), so it restates the title rather than stating a verb+resource. It gives no indication of what is actually computed or returned, and does nothing to separate it from the many other hellenistic_schmidt_* siblings.

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 any alternative tool. An agent has no basis for choosing this over astroway_hellenistic_schmidt_sect_classes or any other Schmidt-tradition sibling.

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