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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe, non-destructive read. The description adds value by explaining it returns precise ingress timestamps (not just positions), and the detailed parameter descriptions (especially ayanamsa and nodeType) transparently explain configurable behavior. The description doesn't contradict annotations, and there is no mention of return format or pagination, but with annotations covering safety and the schema covering parameters, this is complete.

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 concise (4 sentences) and front-loaded: the first sentence immediately states the core function (track ingress times). Every sentence adds value—use cases, specific applications—without redundancy or fluff.

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?

Given the tool's moderate complexity (7 parameters, 3 required) and the absence of an output schema, the description adequately explains the purpose and typical use cases. It doesn't describe the exact return format (e.g., list of timestamps), which would be helpful, but the use cases and parameter coverage are complete enough for most agents. A 5 would require return format details.

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 description coverage is 100%, so baseline is 3. The description goes beyond the schema by explaining the purpose of the tool and how the parameters relate to use cases, e.g., tracking Sun sankranti (which ties to endDate/startDate and planet). Parameter descriptions themselves (like ayanamsa's detailed explanation) are rich and add meaning. This represents a net positive addition, earning a 4.

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 tracks when planets enter new zodiac signs with precise ingress timestamps, using a specific verb ('Track') and resource ('rasi ingress times'). It effectively distinguishes from siblings by focusing on ingress timestamps rather than chart positions (like post_vedic_astrology_kp_planets) or sub-lord changes (post_vedic_astrology_kp_sublord_changes).

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 explicitly states it is essential for transit analysis, muhurta selection, and predictive readings, and gives concrete use cases like Sun sankranti dates, Moon sign changes for panchang, and outer planet transits. However, it does not explicitly state when NOT to use this tool or name specific alternatives among the 47 siblings, though the context implies it against the sibling list.

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