Panchang: Gowri Panchangam (Gowri Nalla Neram)

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the bar is low, and the description still adds real context: the sunrise-to-sunrise segmentation rule, the merging of neighbouring good segments into nallaNeram, cross-validation against drikpanchang Chennai and Delhi, the POST endpoint, and a 20-credit Tier 2 cost. What is missing is any note on segment boundary conventions or precision limits of the derived timings.

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 core sentence is dense but front-loaded with the resource definition and the good/bad classification, and the bracketed metadata lines (group, endpoint, required, cost) are compact and operationally useful. It could be tightened by moving the segment-name list later or trimming the drikpanchang provenance note.

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?

An output schema exists, so return values need not be explained, yet the description still characterizes the returned windows and the merged nallaNeram list. Cost, endpoint, and required inputs are stated. The remaining gap is guidance on choosing this tool over the other panchang timing tools.

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 57%, so baseline is 3. The description contributes only the implicit point that location drives the sunrise/sunset boundaries and restates the three required parameters already marked required in the schema; latitude and longitude carry no descriptions anywhere, and the ayanamsa/timezone interactions are handled entirely by the schema, not the description.

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 specific resource (Tamil Gowri Panchangam) and details exactly what it produces: day and night each split into 8 equal segments with weekday-table names, good/bad classification (Amirdha, Uthi, Laabam, Dhanam, Sugam vs Rogam, Soram, Visham), plus merged nallaNeram windows. This is far more than a restatement of the title. It does not, however, distinguish the tool from panchang siblings such as hora, choghadia, or rahu_kaal, so the agent gets no routing signal.

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 explicit when-to-use statement, no prerequisites, and no named alternative. The 'Tamil' qualifier and the good/bad segment vocabulary imply the domain (choosing auspicious time windows), but the agent must infer that this is the right panchang tool rather than choghadia, hora, or the full panchang.

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