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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful domain context (preferred nakshatras, avoided weekdays) but says nothing about the output's structure, ranking behavior, or how topN and the search window interact, leaving behavioral gaps.

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?

Very concise — two sentences plus group/cost tags — with the purpose front-loaded. No wasted words, though the nakshatra list dominates and could have been summarized or deferred to a reference.

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 return values needn't be explained. However, with 10 parameters, only 1 required, and just 40% schema coverage, the description does little to close the parameter gap or clarify how the geographic/timezone inputs affect results. It is adequate but leaves meaningful context missing.

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%, so several parameters (latitude, longitude, search_window_start/end, topN, ayanamsaId) lack documentation in both schema and description. The description adds no parameter-level guidance at all, offering no compensation for the low coverage.

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+resource: an auspicious-window scanner for property purchase / Griha Pravesh, which is clearly distinct from the many muhurat siblings (marriage, vehicle, travel, etc.). The purpose is unambiguous, though it doesn't name the sibling it competes with directly.

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 implies when to use it (planning a property purchase or housewarming) and gives the auspicious criteria, but provides no explicit when-to-use vs. alternatives, no prerequisites, and doesn't distinguish from astroway_reports_muhurta or astroway_vedic_muhurat_general_auspicious.

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