Panchang: Chandrashtama of the day

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds two useful extras beyond that: the Tamil daily-sheet formatting convention for the output and a concrete cost of 20 credits (Tier 2). It says nothing about error conditions, precision of the sunrise computation, or how ayanamsa choice affects results.

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?

A single front-loaded sentence states the payload, followed by compact bracketed metadata for group, endpoint, required inputs and cost. No filler prose; the bracketed block is scannable rather than verbose.

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 needn't be explained, and the cost/endpoint block is present. However, for a sunrise-boundary, location-dependent tool with seven parameters, the definition gives no indication of how latitude/longitude or ayanamsa selection influences the result, leaving meaningful gaps an agent cannot fill.

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?

Seven parameters with only 57% schema description coverage, and the description adds no meaning to any of them. The only parameter-adjacent statement (the sunrise-to-next-sunrise day boundary) merely restates the date field's schema description. The ayanamsa/ayanamsaId duplication and timezone vs timezoneOffset precedence are left entirely to the schema.

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 the specific resource (Chandrashtama for the day) and its scope (sunrise to next sunrise, per Moon sign, with nakshatra padas), so an agent can tell it produces a daily Chandrashtama listing. It does not distinguish itself from the sibling astroway_vedic_panchang_chandrashtama, and the phrasing 'the rashi that has Chandrashtama' is slightly ambiguous about whether one or several rashis are returned.

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 when-to-use or when-not-to-use guidance, and no named alternative. An agent must infer from the tool name alone whether this or the non-'day' chandrashtama sibling is the right call.

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