divine_get_planetary_positions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds return-content context but no behavioral caveats such as the effect of node_type on Rahu/Ketu calculations or any prerequisites beyond the schema.

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 short, purposeful sentences with no filler. It front-loads the action and resource, then compactly lists the return scope and fields.

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?

With an output schema present and annotations covering safety, the core purpose is adequately described. However, given the large set of sibling planetary-position tools, the description would benefit from explicitly stating that this is the standard Vedic birth-chart version or noting the optional node_type calculation method.

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?

Input schema coverage is 100%, so both the 'params' object and 'node_type' parameter are already documented with descriptions and defaults. The tool description adds no parameter-level meaning, but the baseline of 3 is appropriate since the schema carries the full burden.

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?

Description states a clear verb ('Get') and resource ('planetary positions in the birth chart'), and specifies exactly which nine planets and which fields are returned. It implicitly distinguishes this from matching or annual tools, but it does not explicitly differentiate it from other planetary position siblings like divine_get_kp_planetary_positions or divine_get_lal_kitab_planetary_positions.

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 guidance on when to use this tool versus alternatives. It does not mention that this is the standard Vedic birth-chart position tool or name any sibling tools to avoid, such as divine_get_kp_planetary_positions or divine_get_varshphal_planetary_positions.

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