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

With no annotations, the description carries the full behavioral burden. It discloses the numeric input convention for signs and nakshatras, explains that the response is a reason rather than a judgment, and warns that an unresolved case is reported as 'unexplained' without retrofitting. This is meaningful transparency, though it does not discuss side effects, required parameter combinations, or error handling in depth.

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 somewhat long but well structured: it opens with the core purpose, then gives parameter conventions, and closes with limitations and fallback behavior. The emojis and disclaimers add useful emphasis rather than pure filler, though a few ideas are restated.

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?

The description covers purpose, numeric input conventions, checked factors, and fallback behavior, which is fairly complete for a niche verification tool. Yet given the tool has 10 parameters, no annotations, and no in-schema descriptions, the absence of guidance on how parameters combine (e.g., chart_id versus date/time/place, geonameid usage) is a notable completeness gap.

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 usefully explains that signs and nakshatras are passed as numbers (0–11 and 1–27), and it relates ayanamsa and time calculations to the verification logic. However, several parameters such as chart_id, geonameid, lang, date, time, and place receive no explicit semantic explanation, leaving gaps for an agent to infer.

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 identifies the tool's function: it explains why an externally provided chart does not match the calculated chart and returns the reason for the discrepancy. It specifies what is checked (reference school and time handling) and explicitly distinguishes itself from a verdict tool, but it does not directly name or contrast sibling tools.

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 gives clear usage context: use it when someone supplies foreign chart numbers and wants to understand why they differ. It also states exclusions — it does not decide who is right, and it does not force an explanation when no cause is found. However, it does not explicitly describe alternatives among sibling tools.

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