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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description usefully adds the cost (20 credits, Tier 2), the POST endpoint, and the required inputs, but says nothing about output shape, computation caveats, or what 'Atmakaraka/Darakaraka highlighted' changes in the payload. Adds some value beyond annotations, not rich context.

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?

Front-loaded with the purpose and the sibling comparison in the first sentence, then tight metadata lines for group, endpoint, required params, and cost. No filler prose; the only slight cost is the redundant restatement of required parameters already in the schema.

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 and annotations carry the safety profile, so the description does not need to explain returns. It is adequate but thin for a 15-parameter, credit-charged calculation tool: it omits how ayanamsa/house-system choices affect the karaka ranking and never spells out what the 'focused' output contains.

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?

15 parameters with only 33% schema description coverage, so the description should compensate for undocumented params (houseSystem, zodiacType, ayanamsaId, cosmogram, city, name). Instead it only restates the four required fields, which the schema already declares, adding zero meaning for the remaining eleven.

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 specific verb+resource ('detailed chara karaka ranking') and names the sibling it overlaps with ('/karakas', i.e. astroway_vedic_jaimini_karakas), asserting it returns a focused AK/DK view instead. The only weakness is that 'focused output' is never concretely described, so the exact delta from /karakas is left to inference.

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?

The phrase 'focused output for AK/DK-driven analyses' implies when this tool is preferred, but there is no explicit when-to-use statement or when-NOT-to-use condition (e.g. 'use /karakas for the full ranked table of all karakas'). The guidance is implied rather than stated.

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