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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety surface is covered. The description adds cost context (20 credits, Tier 2) and domain framing, but it does not disclose any behavioral traits beyond that, such as computational assumptions or what the output contains. With annotations carrying the main behavioral load, this is adequate but not rich.

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 short and front-loaded with the domain definition, followed by group and cost metadata. Every line earns its place, though its brevity is partly due to under-specification rather than disciplined concision. Structurally it is clean and easy to scan.

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-format details need not be in the description, and annotations cover the safety profile. However, for a 15-parameter tool with low schema description coverage and many sibling Panchang tools, the description omits usage context, required-input expectations, and alternatives. It is not complete enough to guide correct invocation confidently.

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 schema has 15 parameters with only 33% description coverage, and the tool description provides no parameter guidance at all. It says nothing about required inputs (date, time, latitude, longitude) or important optional controls such as ayanamsa, timezone, fields, precision, or houseSystem. For a high-parameter tool with sparse schema descriptions, the description fails to compensate.

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 defines the domain concept (karana as a half-tithi, its 1-60 range, and the movable/fixed classes) but never states the tool's action, such as calculating or returning the current karana for a given time and place. It distinguishes karana from tithi and yoga by name, yet an agent must infer that this tool produces a karana result rather than another Panchang element. The purpose is recognizable but not explicit.

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 guidance on when to use this tool versus siblings like astroway_vedic_panchang_tithi, astroway_vedic_panchang_yoga, or astroway_vedic_panchang_full. The description gives no conditions, prerequisites, or alternatives, leaving the agent to guess from the name alone.

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