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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the tradition grouping and the 10-credit/Tier 1 cost, which is real behavioral context an agent can act on for budget decisions, but it discloses nothing about the computed output, determinism of results, or data requirements.

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?

Two short bracketed metadata lines plus a one-line purpose — tightly sized and front-loaded with no filler. It is terse rather than verbose, though the metadata lines consume most of the available space where substantive content could have gone.

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 low schema description coverage, the description is far too thin: no input guidance, no when-to-use, no note on how the day/night/common variant is chosen (presumably from chart sect). An output schema exists, so return values need not be explained, but the rest of the burden is unmet.

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 is the only place left to explain inputs — and it says nothing about any of them. The four required fields (date, time, latitude, longitude) and the many optional chart modifiers (zodiacType, houseSystem, ayanamsa, fields, precision) are left entirely to the partial schema, which does not compensate for the low coverage.

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 line 'Dorothean triplicity rulers (day/night/common)' names a specific Hellenistic technique and its three sect variants, so an astrologically literate agent can tell it apart from siblings like hand_bounds or decanic_rulers. However, it is essentially a restatement of the title with no verb — it never says what the tool computes or returns (e.g. the triplicity lord per planet/sign), leaving purpose inferred from jargon rather than stated.

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 technique versus alternatives (e.g. almuten, bounds, sect strength) and no prerequisites. The only routing help is the parenthetical noting it is an alias of `astroway_hellenistic_brennan_triplicity_rulers`, which is useful for de-duplication but is not usage guidance.

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