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 genuine behavioral value by disclosing the return content (running now, three phases with dates, next occurrence) and the birth-data requirement, though it doesn't say what happens with an imprecise birth_time.

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?

Front-loaded usage triggers, then return shape, then inputs — three tight sentences with no filler. Nothing is wasted, and the routing-critical condition comes first.

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?

No output schema exists, and the description compensates by summarizing the return (current status, three phases with dates, next occurrence). Annotations cover the safety profile and the schema covers inputs, so an agent has everything needed to call this correctly.

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 coverage is 100%, so the schema already documents format and examples for birth_date, birth_time and birth_place. The description only restates 'needs birth date and town' and adds no format or accuracy guidance beyond the schema, so the baseline 3 is appropriate.

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 a specific verb+resource (check Sade Sati / Saturn's 7.5-year transit) and gives the exact user phrasings it maps to, including 'Shani sade sati'. It is clearly distinguishable from siblings like saturn_return_dates and manglik_check.

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?

Explicitly states when to use it via multiple trigger phrases ('whether they are in Sade Sati', 'when it starts or ends', 'seven and a half years'), which is exactly what an agent needs for routing. It also states the required inputs at the end.

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