divine_get_shadbala

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, lowering the bar. The description adds that the tool calculates six named strength types for each planet, but does not disclose output format, required assumptions, or limiting behaviors.

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 concise sentences with the primary action front-loaded. The second sentence adds detail by naming the six Shadbala components; only minor redundancy exists between 'six-fold strength' and the enumeration.

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?

The description is adequate for selecting this tool when Shadbala is requested, and an output schema exists to fill in return-value details. However, it does not place this tool among its many siblings or call out that full birth details are required, leaving an agent to rely on the schema for invocation context.

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?

The top-level 'params' property has no description and schema coverage is 0%. Although nested KundliInput fields have descriptions, the tool description only says 'for a birth chart' and provides no direct guidance on required inputs, so it fails to compensate for the low 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 uses a specific verb and resource: 'Get Shadbala (six-fold planetary strength)', then enumerates the six strength types. This makes it clearly distinguishable from sibling tools like divine_get_bhav_bala or divine_get_planet_analysis.

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 guidance is given about when to use this tool versus the many related astrological strength/analysis tools. The description implies use when Shadbala is needed, but does not state exclusions or name alternatives.

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