divine_get_prasthara_chakra

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety behavior is covered. The description adds useful behavioral context by specifying that it shows a detailed breakdown of benefic contributions, which is richer than a mere summary. No contradiction with annotations.

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 tight, front-loaded sentences that state the purpose and the output substance with no filler. The structure allows an agent to quickly grasp what the tool provides.

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?

For a read-only, idempotent tool with an output schema and a detailed input schema, the description covers the core computation and output. It is not fully complete because it lacks explicit sibling differentiation and when-to-use guidance, but the structured fields supply the remaining operational detail.

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 description only says 'for a birth chart' and gives no detail about the params object; with schema description coverage reported as 0%, it does not compensate. The nested KundliInput schema contains field descriptions, but the description itself adds no parameter-level meaning beyond that.

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 clear verb and resource: 'Get Prasthara Chakra (expanded Ashtakvarga)' and explains it shows benefic contributions per planet to every sign. It is specific enough to be understood, but it does not explicitly position itself against sibling tools such as divine_get_ashtakvarga or divine_get_sarvashtakavarga.

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 'for a birth chart' and 'detailed breakdown' imply when to use it, but there is no explicit guidance about alternatives or exclusions. Given the large sibling list, an agent must infer that this tool is for the expanded per-planet/per-sign view rather than a summary Ashtakvarga.

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