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

Annotations already establish that this is a safe, read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds genuine behavioral context by naming the methodology (BPHS Adhyaya 34 kendradhipati and maraka rules) and the exact scope of the payload (7 visible grahas), but it says nothing about permissions, latency, or determinism beyond what annotations supply.

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?

Purpose is front-loaded in the first phrase, followed by a compact enumeration of return fields, and the group/cost metadata is clearly delineated. Slightly dense with domain jargon but no wasted sentences.

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 the description is not obligated to explain return values, yet it does so helpfully. However, for a 15-parameter astrological calculation where ayanamsa and house system change results, the absence of any parameter or setup guidance leaves a real gap for correct invocation.

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 contributes zero parameter information — no mention of birth data, ayanamsa selection, or zodiac/house-system choices that materially affect this Vedic calculation. With 15 parameters including three enums, the description fails to compensate for the thin schema coverage.

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 a specific analytical output: functional benefic/malefic identification based on Lagna-lord ownership, and enumerates the returned data (natural nature, functional nature categories, houses owned, reasoning). It is clearly distinguishable from generic Jaimini yoga tools, but it never explicitly contrasts itself with the many sibling yogas/dignities tools (e.g. astroway_vedic_jaimini_yogas, astroway_vedic_jaimini_karakas).

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 named alternatives among the large family of Vedic/Jaimini siblings. The reader must infer from the title that this is the tool for functional nature classification rather than, say, karakas or raja-yoga detection.

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