Panchanga

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds that it returns data in UTC but does not elaborate on edge cases, input validation, or output structure beyond the listed elements. No contradiction with annotations.

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 single, direct sentence with no filler. It states the action, key input constraints, and output elements efficiently.

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 description lists the output elements and specifies UTC, which is useful. It does not discuss error scenarios or validation details, but for a simple computation tool, the provided context is adequate.

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?

The input schema has 100% description coverage, so the baseline is 3. The description mentions 'one calendar date' and 'geographic location' mapping to the location object, but adds little beyond the schema's per-field descriptions.

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 Panchanga elements for a single calendar date at a geographical location, listing specific outputs (tithi, vara, nakshatra, yoga, karana, end times). This differentiates it from the sibling asterwise_get_panchanga_calendar, which covers a whole month.

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 a single date but does not explicitly contrast with alternatives like asterwise_get_panchanga_calendar or asterwise_get_tamil_panchanga. No explicit 'when to use vs. when not to use' guidance is provided.

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