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

With readOnlyHint/idempotentHint/destructiveHint already declared, the description's additional disclosure of the 250-credit tier and the explicit confirm-with-user instruction is genuinely useful behavioral context that annotations cannot carry. It stops short of describing runtime characteristics such as latency or failure modes, and does not contradict any annotation.

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?

One sentence of real description followed by compact bracketed metadata; the technique and its mechanism are front-loaded. No filler sentences and every bracketed field (group, endpoint, required, cost) is actionable.

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 no explanation, and annotations cover the safety profile, leaving the cost/confirmation note and required-param list to round things out. It still leaves a gap on how the result relates to the caller's inputs — e.g., whether settings like zodiacType or ayanamsa change the derived time — which matters for a 15-parameter endpoint.

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 coverage is only 33% across 15 parameters, so the description must compensate; it does so partially by naming the four required inputs (date, time, latitude, longitude). It adds nothing about the many optional knobs (fields, precision, zodiacType, houseSystem, timezone/offset, ayanamsa) that a caller of a rectification technique may need to set deliberately.

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?

States a specific verb (derive) and a specific resource (birth time) via a named technique, the Trutine of Hermes (Animodar), and explains the underlying mechanism (Moon's prenatal syzygy). It does not explicitly contrast itself with the closest sibling, astroway_prognostics_rectification, so an agent must infer the relationship from the technique name alone.

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 '⚠️ Heavy — confirm with user before invoking' note plus the 250-credit cost gives real invocation guidance, and the required parameters are listed inline. However, there is no statement of when this technique is preferable to astroway_prognostics_rectification or the other prognostics tools, and no prerequisites (e.g., that a birth time is what is being solved for).

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