divine_get_jaimini_planetary_positions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the tool is known safe. The description adds that it returns Karakas based on planetary degrees, which is useful context not in annotations. However, it does not disclose any other behavioral aspects like response format or potential errors. With annotations covering safety, this is acceptable, but it could add more context about what 'Jaimini-specific' entails.

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 two sentences, front-loaded with the tool's purpose and then an example of what it returns. It is concise, but the second sentence could be more informative about usage. Still, it is efficient with minimal waste.

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 input schema (KundliInput) is well-documented, the description covers the purpose and return concept. It lacks explicit detail on how node_type affects karaka calculation, but for a read-only tool with rich schema, this is fairly complete. It could mention that it's distinct from standard planetary positions, but that's already in purpose.

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 has 100% description coverage, with the 'params' object (KundliInput) describing birth details and 'node_type' describing the mean/truenode option. The description adds that planetary degrees are used for karaka calculation, but gives no extra meaning for parameters beyond the schema. Baseline 3 is appropriate due to high 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 clearly states it gets Jaimini-specific planetary positions and karakas, specifically Chara Karakas. It distinguishes from siblings like divine_get_planetary_positions and divine_get_jaimini_padas. The specificity of 'Jaimini-specific' and listing examples of karakas makes it unambiguous.

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 implies this tool is for Jaimini karaka calculations, but does not explicitly state when to use it versus siblings like divine_get_planetary_positions or divine_get_jaimini_padas. Given the large number of siblings, clearer differentiation would help an agent choose correctly.

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