check_sade_sati

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

No annotations are present, so the description must convey behavior. It states the tool returns current status, phase, and dates, disclosing the core output. However, it does not disclose potential errors, edge cases (e.g., if Moon sign cannot be computed), or any limitations. The description does not contradict any annotations.

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 compact at three sentences, front-loading the purpose and key details. Every sentence adds value: definition, significance, and expected output. No extraneous information.

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 complexity (astrological computation with 5 required params), the description adequately explains the concept and output. With full schema coverage and no output schema, the description compensates by listing return fields. Could mention that the tool uses all params to compute the Moon sign and Saturn transit, but overall sufficient for an agent to invoke 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?

All 5 parameters have schema descriptions (100% coverage), so the baseline is 3. The description does not add additional meaning beyond the schema; it does not explain how the parameters are used (e.g., to compute Moon sign or Saturn position). Thus, no boost beyond baseline.

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 it checks if a person is currently in Sade Sati, defined as the 7.5-year period when Saturn transits sign positions relative to the natal Moon sign. It also specifies what is returned (status, phase, dates), and the mention of Vedic astrology context differentiates it from other check tools like check_kaalsarp_dosha or check_mangal_dosha.

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 defines the tool's purpose and indicates it is for Vedic astrology, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., get_planet_transits) or mention prerequisites like requiring a known birth time. Usage is implied for astrological assessment of Saturn's influence.

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