Muhurat: Long journey (multi-day Yatra)

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for the domain rules instead: Friday exclusion and the eight preferred nakshatras. It also discloses the 50-credit Tier 3 cost and the POST endpoint, which the annotations do not carry.

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 lead sentence front-loads purpose and scope, then the qualifying rules, with no filler. The bracketed metadata block is terse, though the 'Required' line duplicates the schema and could be dropped.

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?

An output schema exists, so the return values need no explanation, and the safety profile is covered by annotations. What is missing is guidance on the opaque 7-of-8 parameters, particularly the date window and location inputs that would change results.

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 only 25%, so the description should compensate, but it adds meaning for essentially no parameters. 'Required: search_window_start' merely repeats the schema's required list; topN, latitude, longitude, ayanamsaId, and search_window_end are not explained at all (e.g., whether end is optional or how wide the window may be).

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?

States a specific verb and resource: 'Auspicious-window scanner for multi-day journeys (pilgrimages, relocation travel)', which is distinct from the sibling muhurat tools. The parenthetical examples pin down the scope of 'long' unambiguously.

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?

Explicitly positions itself against the short-travel variant ('Stricter than short travel: Friday is excluded per Yatra prakarana'), which tells the agent this is the multi-day route. It never names astroway_vedic_muhurat_travel as the alternative for short trips, so routing is implied rather than spelled out.

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