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 fully covered by structured data. The description adds no behavioral context beyond that — no note on computational cost, precision sensitivity to birth time (relevant for arudha/pada calculations), or determinism caveats.

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 fragments, no filler, with the core resource (Arudha/Upapada) front-loaded. It is efficient, though the extreme brevity is part of why the other dimensions are thin.

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 not be explained, and the schema documents most inputs. Still, for a birth-data-driven analysis tool sitting among many look-alike siblings, the description omits what makes this output distinct and what inputs it depends on, leaving it only minimally complete.

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 75% with 8 parameters, and the description contributes nothing about any of them — not the date/time/location requirement, not the place-vs-coordinates branch of the anyOf. It does not compensate for the parameters that carry no schema description (latitude, longitude).

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 domain artifacts computed: Arudha Lagna, Upapada, all twelve padas, and Jaimini rashi drishti. An agent can tell this is a Jaimini arudha-structure analysis, which separates it from generic siblings like analyze_house or calculate_strength_profile. It does not, however, distinguish itself from the close sibling calculate_jaimini or analyze_special_points.

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 guidance, no prerequisites, and no mention of alternatives among the ~80 sibling analyzers. The agent is left to infer that this is a specialized structural read, with nothing stating when it should be preferred over calculate_jaimini or analyze_special_points.

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