divine_get_surya_nakshatra

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

The annotations already establish a safe, read-only, idempotent operation. The description adds the useful behavioral fact that it returns the nakshatra occupied by the Sun, but it does not disclose details like precision, result structure, or language behavior beyond what the output schema would already provide.

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?

Two sentences with no filler; the core action and resource are front-loaded. The second sentence earns its place by stating the output and an analytical use case.

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?

Inputs are all captured by the schema and the output schema covers the return shape, so the description does not need to explain those. It is near-complete for a safe read-only lookup, though it could more explicitly differentiate itself among the many sibling tools.

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?

With schema description coverage reported at 0%, the description needed to compensate for parameter documentation, but it only vaguely references 'date and location' and omits timezone, language, and value formats. No parameter-level meaning is added beyond a high-level input summary.

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 opens with a specific verb and resource: 'Get Surya (Sun) Nakshatra details for a given date and location,' which clearly identifies what the tool returns. It does not explicitly contrast it with siblings like divine_get_nakshatra or divine_get_month_surya_nakshatra_list, so it stops short of full differentiation.

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 phrase 'useful for solar-based astrological calculations and rashi sandhi analysis' gives clear context for when this tool is appropriate. It does not, however, provide when-not-to-use guidance or point to alternatives among the large sibling suite.

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