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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds meaningful behavioral context beyond that: it only reports the current phase and deliberately avoids remedies or fear language, setting output-scope expectations. It does not describe response formatting, but that gap is minor given the annotation coverage.

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?

It is front-loaded with the trigger intent and the input requirement, and every sentence serves selection or scoping. The quoted user phrasings add some length but do real work for intent matching, so the size is justifiable.

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?

With no output schema, the description carries the return-value burden and does state that it reports the current phase only. Combined with the annotations, an agent has enough to call it correctly; only the exact response shape is unspecified.

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 all four parameters (date, time, rashi, placeName) are already documented in the schema. The description's 'rashi OR birth details' note restates what the schema's rashi description already says, adding no new syntax or format detail, so the baseline 3 applies.

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 states a specific verb and resource (check whether sade sati is running, report its current phase) tied to Saturn's transit over the moon sign. It distinguishes itself from adjacent domains by ruling out general Saturn news and Western astrology, though it does not explicitly differentiate itself from the sibling tools like naksha_chart or naksha_daily.

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?

It gives concrete trigger phrases the user might say, specifies the required input either as rashi or birth date/time/city, and includes an explicit exclusion ('Do not use for general Saturn news or for Western astrology'). This is exactly the when/when-not guidance an agent needs.

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