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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely useful behavioral context beyond that: the computation is geographically scoped to India and timezone-anchored to IST, which matters because sunrise/sunset and muhurat windows are location-dependent while the schema exposes no location parameter.

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?

One sentence, front-loaded with the resource, then the return contents. Every clause carries information and nothing is redundant.

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 no output schema, the description compensates by enumerating the returned panchang elements, and the sole parameter is fully specified. Adequate for a zero-required-parameter query tool; it only lacks any note on how muhurat windows are scoped or bounded.

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% — the single 'date' property already documents the YYYY-MM-DD pattern and the today/IST default. The description restates the default ('default today, India') without adding format or boundary detail, so the baseline 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?

Names the resource (Daily Hindu Panchang) and enumerates exactly what it returns — tithi, nakshatra, yoga, karana, vaar, sunrise/sunset, muhurat windows — so the agent knows precisely what it gets. It does not, however, distinguish itself from siblings like shubh_muhurat or muhurat_karma_list that also surface muhurat-related data.

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?

Usage is implied: this is the baseline daily almanac, and 'default today' signals the no-argument case. There is no explicit statement of when to prefer this over the many muhurat-finding siblings, nor any exclusion or prerequisite.

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