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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine behavioral context beyond that: the scan returns the 'top auspicious days within any caller-supplied window' and discloses cost/tier ('50 credits (Tier 3)'), which is valuable for an agent deciding whether to invoke it.

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?

Purpose is front-loaded in the first sentence, followed by the nakshatra note and the orthodox-timing caveat, then group/cost tags. All three sentences carry useful information, though the orthodox-practice note is more context than operational guidance.

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?

With an output schema present, the return values need not be explained, and annotations cover the safety profile. The description supplies adequate domain framing (ceremony scope, nakshatra acceptance, window behavior) for a muhurat scanner, though it leaves the 10-parameter surface largely to the schema.

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 40% across 10 parameters, so the description is expected to compensate but does not. It alludes vaguely to 'any caller-supplied window' (the search_window params) but adds no meaning for topN, ayanamsa, timezoneOffset, precision, fields, or latitude/longitude beyond what the schema already states.

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 gives a specific verb+resource ('Auspicious-window scanner for Namkaran') and names the ceremony, which meaningfully separates it from the many other muhurat siblings (marriage, travel, surgery, etc.). However, it does not explicitly distinguish itself from the potentially confusable siblings astroway_vedic_muhurat_name_change or astroway_vedic_muhurat_general_auspicious.

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 note that 'orthodox practice schedules Namkaran on the 11th or 12th day after birth' gives useful domain context, and the tool scans a caller-supplied window. But there is no explicit when-to-use / when-not guidance and no routing to sibling muhurat tools, leaving the agent to infer usage from the name alone.

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