Muhurat — Business start (Vyapara)

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

Annotations indicate readOnlyHint=true and idempotentHint=true, so the tool is safe. The description adds behavioral context by listing preferred nakshatras and avoidance days, but does not disclose what happens if no windows are found or how scoring works beyond an unclear 'same scoring shape.' It does not contradict 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 around 100 words and includes an example, list of nakshatras, and cost, making it fairly efficient. However, the phrase 'Same scoring shape' is unclear and could be expanded or removed. Front-loading is adequate with the main purpose stated first.

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 tool has 7 parameters and no output schema, yet the description does not explain what the tool returns (e.g., list of dates with scores). It mentions 'scoring shape' but never defines the output. Given the complexity, the description leaves significant gaps for an AI agent to understand the full context.

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, but it only provides an example JSON body without explaining any parameters individually. Users are left to infer meaning from the example, which is insufficient for 7 parameters including optional fields like ayanamsaId and topN.

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 is an 'auspicious-window scanner for starting a business / new venture,' providing a specific verb and resource. It further distinguishes itself from sibling muhurat tools by specifying nakshatras and days to avoid, making its purpose distinct.

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 an example request body and mentions it's for business start, but does not explicitly state when to use or not use this tool versus alternatives like vedic_muhurat_investment or vedic_muhurat_general_auspicious. The phrase 'Same scoring shape' is ambiguous and provides no comparative guidance.

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