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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that calculations are 'accurate based on observer location,' which hints at positional dependence, but it does not disclose return format, potential errors, or rate limits. No contradiction with annotations; this is adequate but not rich behavioral context.

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 a compact list of the tool’s rich output domains, followed by use cases. It is longer than a simple one-liner but each clause conveys distinct information. Structure is decently front-loaded: the main result type and scope appear first, and use cases come at the end. A slight redundancy is that 'complete' and the enumeration both emphasize comprehensiveness.

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 that the tool has no output schema and the input schema is already detailed, the description does a good job of telling the agent what data will be returned (five limbs, onset time, etc.) and why the tool matters. It lacks an explicit comparison to panchang_basic/choghadiya/hora and does not describe the response shape, but for a read-only astrological data tool this is close to complete.

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 100%, with each parameter already well-documented, including the impactful timezone behavior. The tool description adds no additional parameter-level meaning beyond saying calculations depend on observer location, which is a minor reinforcement. The baseline of 3 is appropriate.

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 what the tool returns: a complete daily panchang with all five limbs, sunrise/sunset/moon times, inauspicious and auspicious periods, and planetary hora. The word 'complete' and the enumerated components help distinguish it from the panchang_basic and panchang_hora siblings, though it does not explicitly name those alternatives.

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 gives concrete use cases: 'muhurta selection, daily horoscope apps, Hindu calendar integration, and electional astrology.' This communicates when to use it, but it does not state when not to use it or name alternative panchang tools, so it stops short of full exclusion guidance.

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