get_panchanga_shuddhi

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

No annotations provided, so description bears full burden. It explains all rules for each limb, value at sunrise, and system default. No destructive behavior, and the assessment logic is fully disclosed.

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?

Description is comprehensive but somewhat lengthy. It front-loads purpose and verdicts, then rules per limb. Could be more concise, but structured well for a complex tool.

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 complexity and presence of output schema, description fully covers input parameters, rules, and output format. Provides enough information for an agent to select and invoke the tool correctly.

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 coverage is 0%, so description must compensate. It explains date format, city (or lat/lon), and system default, but does not describe the 'timezone' parameter. Overall adds significant meaning beyond schema but leaves a gap.

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 the tool assesses 'Panchanga Shuddhi — five-limb purity assessment' for a given date, with specific verdicts and per-limb breakdown. It is distinct from sibling tools like get_panchangam or find_muhurta.

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 usage for evaluating purity of a date's panchanga limbs, but does not explicitly mention when to use alternatives or provide exclusions. However, the detailed rules and parameters give sufficient context for agent decision.

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