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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds two genuinely useful pieces beyond that: the credit cost (20, Tier 2) and the backing endpoint. It still says nothing about compute weight or what the cascade returns, but with rich annotations and an output schema the bar is lower.

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?

Four short lines, front-loaded with the purpose, with no filler sentences. The bracket lines are terse and scannable, though they are largely boilerplate rather than substance, which keeps this just short of a 5.

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?

Annotations, a full input schema and an output schema mean return values and safety need not be explained, and cost/endpoint are covered. What is missing is the one thing this description uniquely must supply: how Sookshma differs from the other four Sthira levels and from the ~30 sibling dasha tools. Without it, an agent in this namespace cannot select correctly.

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?

All 3 top-level parameters (body, fields, precision) carry full schema descriptions, including detailed birth-data rules, the fields dotted-path compact mode and precision rounding. The description adds nothing about parameters, but the baseline is 3 when schema coverage is 100% and the schema does the work.

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 dasha system and level and adds that it is a '4-level cascade', which hints at the depth of sub-period breakdown. However, it never explains what Sthira Sookshmadasha means relative to its near-identical siblings (sthira_maha, sthira_antar, sthira_pratyantar, sthira_prana), so an agent cannot distinguish this from four other Sthira tools. Vague rather than misleading.

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 statement, no prerequisites, and no mention of alternatives such as the coarser Sthira levels. The bracketed lines give group, endpoint and cost, which is operational metadata, not usage guidance. The agent is left to infer selection entirely from the tool name.

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