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

Annotations already declare readOnly/idempotent/non-destructive. The description adds practical context: POST endpoint, required parameters, 20-credit Tier 2 cost, and the division/cycle model. It still does not explain auth or response behavior, but output schema and annotations carry much of that.

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 first sentence front-loads the core concept, followed by a compact cycle list and bracketed metadata. It is tight and scannable, though the metadata block could be integrated more cleanly.

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?

For a 15-parameter Vedic calculation with no output-schema burden, the description covers the concept and required inputs but omits how this tool relates to other panchang endpoints and how optional astrological settings affect results. Annotations and output schema fill safety/return gaps, leaving usage and parameter context thin.

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?

Coverage is only 33% across 15 parameters. The description repeats the four required parameters already present in the schema and adds no meaning for optional parameters such as ayanamsa, timezone, fields, precision, or houseSystem.

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?

States the specific Choghadia divisions, their count/duration and quality marks, so it is clearly not panchang_full or hora. It does not explicitly name sibling alternatives, which keeps it from a 5.

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 guidance, no contrast with other panchang tools such as hora, karana, tithi, rahu_kaal, or yoga. Required inputs are listed, but that is invocation data rather than usage guidance.

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