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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds the 20-credit Tier 2 cost and the output-depth trait, which are genuinely useful and not present in the annotations, but says nothing about response size, latency, or validity constraints at minute-scale depth.

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 tight sentences plus group and cost metadata, front-loaded with the technique name and its distinguishing depth trait. Nothing is wasted, though the brevity leaves routing gaps that a slightly longer treatment would have closed.

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 schema and output schema are rich, so return values need no explanation, and annotations cover the safety profile. However, for a tool sitting in a five-member Kalachakra family, the description does not tell the agent how this level relates to the other four, leaving the primary selection question unanswered.

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 100% and the nested body schema documents every field (birth data, ayanamsa, timezone, target date/time, fields, precision) in detail, so the schema carries the burden. The description adds no parameter-level meaning beyond that, which is the baseline 3 for a fully documented schema.

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 description names the specific technique (Kalachakra Pranadasha) and characterizes its output depth as a '5-level cascade' at the 'finest grain, minutes-scale'. That meaningfully separates it from the four sibling levels (maha, antar, pratyantar, sookshma) which are not described as finest-grain, though the sibling relationship is never made explicit.

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 guidance on when to choose this tool over the shallower Kalachakra levels or over other dasha systems (vimshottari, ashtottari, etc.). The agent must infer selection from the phrase 'finest grain' alone, with no stated prerequisites or alternatives.

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