Muhurat — Naming ceremony (Namkaran)

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds value by mentioning 'wide nakshatra acceptance per classical text' and credit cost (50 credits), providing algorithmic and pricing context beyond 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 brief and well-structured: first sentence states purpose, followed by a contextual note, group/cost info, and a clear example. No superfluous content.

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 the core concept and provides an example, but it omits details about output format, ranking criteria for 'top auspicious days', or error conditions. Since there is no output schema, the description should hint at return structure, which it does not. Adequate for a simple scanner but not fully 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?

Input schema has 7 parameters with 0% schema description coverage. The description does not explain individual parameters except through the example request body (search_window_start, search_window_end, latitude, longitude, timezoneOffset). Parameters like ayanamsaId and topN are not described. Given the low coverage, the description should compensate but only partially does.

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 Namkaran (naming ceremony)' with specific verb 'scan' and resource 'Namkaran'. It distinguishes from sibling muhurat tools by naming the ceremony type and referencing classical text acceptance.

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 provides usage context by noting orthodox practice schedules the ceremony on the 11th or 12th day after birth, and that the tool scans any caller-supplied window. It implies when to use (post-birth) but does not explicitly state exclusions or alternatives among siblings.

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