find_tarabalam_days

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

With no annotations, the description carries full burden for behavioral disclosure. It details the output (per-day taras, good_for_all_dates, chandra position/verdict) and explains the effect of chandra_mode. However, it omits error handling or rate limits.

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 a single paragraph but is well-organized, front-loading purpose then details. It is concise without being terse, though could benefit from structured bullets for readability.

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 complexity (10 parameters, no annotations, output schema exists), the description covers the main purpose, parameters, and output shape. It does not explain error handling or invalid input behavior, but otherwise is quite complete.

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 0%, so the description must compensate. It adds rich meaning: explains each parameter, gives constraints (e.g., 1-4 nakshatras, canonical spellings, start_date format, days range, city vs lat/lon, system options, chandra_mode options). This goes well beyond the schema.

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 the tool finds auspicious days based on janma nakshatras (Tarabalam) and optionally Chandrabalam. It distinguishes itself from sibling tools like find_muhurta or get_panchangam by focusing on birth-star-based auspiciousness.

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 explains when to use the tool (for auspicious days for one or more people) and how to optionally combine with Chandrabalam. It does not explicitly mention when not to use or alternatives, but the context is clear.

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