Jaimini — Atmakaraka rotation (timeline)

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

Annotations already provide readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds context about the output (timeline with age-of-event, before/after planets, life-event hints) and constraints (default 84 years, cap 120), which is useful beyond the annotations. No contradiction.

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?

The description is concise—three sentences plus group/cost info—and front-loaded with the core concept. Every sentence is informative, with no wasted words. The example further aids understanding without redundancy.

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?

Given the complexity of Vedic Jaimini and the lack of output schema, the description provides the core concept, output content, and defaults, but lacks explanation of the Naisargika progression, interpretation of life-event hints, and details of all parameters. It is adequate but not fully complete for an agent to use without prior domain knowledge.

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 0%, so the description must compensate for parameter meaning. However, it does not explain the 11 parameters (e.g., houseSystem, name, city) beyond showing an example. The description adds no value for parameter semantics, leaving agents to infer from the example.

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 clearly states the tool performs a Naisargika 1°/year symbolic progression and scans for Atmakaraka changes, with a specific verb 'scans' and resource 'Atmakaraka rotation'. The title 'Jaimini — Atmakaraka rotation (timeline)' further clarifies its purpose and distinguishes it from siblings like vedic_jaimini_atmakaraka_navamsa.

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 description does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions. It implies usage for obtaining a timeline of soul-significator transitions but lacks guidance on when to choose it over other Vedic Jaimini tools.

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