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 covered. The description adds provenance context (Jaimini Sutras 2.x, BPHS Adhyaya 47, PyJHora) which helps an agent judge authority, but says nothing about determinism relative to ayanamsa choice or any computation constraints.

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 dense sentences that are front-loaded with the actual output contents, followed by compact group/cost tags. No filler or restatement of the title. Slightly terse on the trailing source citation, but every element earns its place.

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. For a 15-parameter, 33%-documented tool the description is thin: it omits sibling differentiation and any hint that sidereal settings alter the result. Adequate as a minimum-viable definition but with clear gaps.

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 only 33% and the description adds no parameter information whatsoever. It never explains that ayanamsa/zodiacType/houseSystem materially change the karaka ranking, nor what city/name/cosmogram do. With a low coverage rate, the description was expected to compensate and does not.

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?

Names the specific artifact (Jaimini karakas) and enumerates both variants it returns — chara karakas (8-planet ranking, Atmakaraka..Darakaraka) and naisargika karakas (fixed planet→house mapping). That is well beyond a tautology. However it never distinguishes itself from the sibling astroway_vedic_jaimini_chara_karakas, which appears to cover overlapping ground, so an agent cannot tell them apart from the text 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?

No when-to-use or when-not-to-use guidance at all. The description never says which chart context is needed, whether it should be preferred over the chara_karakas sibling, or how it relates to atmakaraka_navamsa/rotation. Only implied usage can be inferred from the content list.

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