Muhurat — Travel (short Yatra)

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds context about the scanning logic (preferred nakshatras, avoided days) and cost. However, it does not describe the output format or what the result contains, which is a gap beyond the annotations.

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 relatively concise with three sentences plus metadata and an example. It front-loads the purpose and includes key astrological details. The list of nakshatras is a bit long but necessary. It could be more structured, but overall efficient.

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 has 7 parameters with no schema descriptions and no output schema, the description is incomplete. It omits critical details like the output format, how latitude/longitude affect results, the significance of topN, and any constraints on the search window. The example helps but does not cover all parameters.

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 provides an example request body but does not explain the meaning of parameters like latitude, longitude, timezoneOffset, or topN. The listed nakshatras and days are not parameters. This leaves the agent guessing about parameter semantics.

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 it is an 'auspicious-window scanner for short / daily travel', with a specific verb and resource. The title 'Travel (short Yatra)' and the mention of preferred nakshatras further clarify the domain. It implicitly distinguishes from the sibling 'vedic_muhurat_journey_long' by focusing on short travel.

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 lists preferred nakshatras and days to avoid, giving some guidance on what makes a window auspicious. However, it does not explicitly state when to use this tool versus other muhurat tools (e.g., for long journeys vs. short trips). The context is implied but not directly stated, leaving ambiguity for the agent.

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