Calculate Panchang

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

Annotations declare readOnlyHint=true, so description's 'Compute' is consistent. The description adds no significant behavioral disclosure beyond what annotations provide, e.g., no mention of no side effects or required permissions.

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 sentences, front-loaded with key purpose and output details, no redundant text. Every sentence adds value.

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 tool has 6 parameters and no output schema. The description explains the return content (panchang JSON with specific fields) and its compatibility with report tools. However, it does not explicitly state that the output can be used as input to report tools, and the ayanamsa parameter is not elaborated beyond schema. Still fairly 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 coverage is 100% with descriptions for all parameters. The description does not add meaning beyond the schema; it briefly mentions place and date but does not explain parameters like ayanamsa. Baseline score of 3 applies.

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 computes daily Panchang for a given place and date, listing specific components (vara, tithi, nakshatra, yoga, karana, sunrise/sunset) and noting the output format is compatible with report tools. This distinguishes it from siblings like calculate_kundali or calculate_dasha.

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 daily Panchang calculation but does not explicitly state when to use or not use this tool vs siblings. It provides no guidance on alternatives or prerequisites.

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