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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds the cost (10 credits, Tier 1) and the endpoint verb, which are real behavioral facts not in the annotations. It does not describe the response shape or any limits, so it is adequate but not rich.

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 bracket-tag format is compact and front-loads the label, group, endpoint, required params and cost in one block, so nothing is wasteful. However, the brevity comes at the cost of substance — it is concise by omission rather than by tight writing, and the key sentence ('Nine fates classification') conveys little.

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 astrological computation with an output schema, the description leaves the core question unanswered: what the 'ennea mooirai' classification is and what an agent gets back. It omits any mention of sidereal/tropical assumptions or house system defaults that materially change the result. The endpoint/cost metadata helps, but the definition is not sufficient to invoke and interpret the tool 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?

With 15 parameters and only 33% schema description coverage, the description needs to compensate, and it does not. It merely repeats the four required parameters (date, time, latitude, longitude) that the schema already marks as required, adding no format, range or meaning for ayanamsa, zodiacType, houseSystem, timezoneOffset or the compact-mode fields.

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 one-line 'Nine fates classification' essentially restates the tool title (Ennea Mooirai = nine fates) without saying what is computed, what chart inputs produce, or what the classification means. Among the many astroway_hellenistic_schmidt_* siblings, nothing distinguishes this tool's output. No verb, no resource specificity beyond a vague label.

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?

The '[Group: Hellenistic: Schmidt tradition]' tag gives weak implied routing among the Schmidt/Brennan/Greenbaum/Hand families, but there is no explicit statement of when to pick this tool over, say, astroway_hellenistic_schmidt_sect_classes or the greenbaum equivalents. No when-not guidance and no prerequisites beyond the required-parameter list.

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