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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds useful analytical context (the Shadbala/classical-minimum methodology and the metrics computed) but says nothing about cost, latency, or failure modes, so it is a modest increment over the annotations.

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 front-loaded sentence with no filler; the core noun ('overall birth-chart strength score') leads and the supporting metrics follow. It is dense but readable, and nothing is redundant.

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?

There is no output schema, so the description carries the return-value burden and does so by enumerating score, grade, strong-planet count, and ranking. Combined with fully documented input params and complete annotations, an agent has enough to call and interpret it, with only the usage-routing gap remaining.

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%, so all 7 parameters (including the note that 12:00 is the conventional unknown-time value and the India=5.5 timezone default) are already documented. The description adds no parameter meaning beyond reusing the concept of 'grahas', so the baseline 3 applies.

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 concrete resource ('overall birth-chart strength') and spells out exactly what the calculation yields: Shadbala average versus classical minimum across 7 grahas, grade, strong-planet count, and ranking. It implicitly contrasts with siblings like planet_strength and lagna_bal via the word 'overall', though it never names an alternative.

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?

No guidance on when to prefer this tool over planet_strength, lagna_bal, or janam_kundali, and no prerequisites or exclusions stated. The agent must infer usage purely from the tool name and the sibling list.

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