get_panchang

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

With no annotations provided, the description carries the full burden. It clearly describes the outputs and their significance (five limbs, plus extras). It does not discuss limits, error cases, or side effects, but the scope is well-defined.

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: first sentence states the core purpose and outputs, second provides context (muhurta). No wasted words, front-loaded with key 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 (multiple outputs, no output schema), the description covers the main return values and purpose. It lacks details on formatting or error handling, but the inputs are fully specified in the schema.

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 baseline is 3. The description does not add extra meaning beyond the schema, but examples are provided in the schema for each parameter, making it clear.

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 explicitly names the resource (Vedic Hindu Panchang) and lists all five limbs (Tithi, Nakshatra, etc.) plus additional outputs (sunrise/sunset, moon sign, festivals). It clearly distinguishes from sibling tools focused on specific astrological checks like mangal dosha or dasha calculations.

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 states it is essential for muhurta (auspicious timing), implying when to use. However, it does not explicitly say when not to use or mention alternatives among siblings, though the tool is unique among siblings for panchang data.

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