get_moon_sign

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

No annotations provided, so description must disclose behavioral traits. It states it uses Vedic astrology and returns sign, degree, nakshatra, and pada, but doesn't mention computational assumptions, precision, or any constraints. Adequate but not comprehensive.

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?

Concise two-sentence description front-loading the core purpose, then adding context and return details. No wasted words.

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 complexity and absence of output schema, the description covers inputs and basic outputs but lacks completeness: does not specify if time zone is required for accuracy, no mention of error handling or edge cases (e.g., ambiguous birth times). Adequate for a simple calculator.

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 parameters are already well-defined in schema. The description adds no further detail on parameters, which is acceptable given high coverage. However, a brief note on the required format (already in schema) is present.

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?

Clearly states the tool calculates the Moon sign (Chandra Rashi) and specifies that it returns sign, degree, nakshatra, and pada. However, it could better differentiate from sibling tools like get_planet_details or get_ascendant, which also return astrological positions.

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?

Implied usage: when you need the Moon sign for Vedic astrology. No explicit guidance on when not to use or alternatives. Given sibling tools that provide planetary positions, a note on preference would help.

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