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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description usefully adds the credit cost (50 credits, Tier 3), which annotations do not convey. However it says nothing about what the scanner returns, how many windows, or date-window requirements beyond the schema.

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?

Two tight sentences plus metadata tags; the purpose is front-loaded and nothing is padded. The nakshatra list is long but is genuine domain payload rather than filler.

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?

Return-value explanation is unnecessary since an output schema exists, and cost is disclosed. But with 10 parameters at 40% schema coverage, the description omits the location/timezone/search-window semantics an agent needs for correct invocation, leaving a real gap for a Tier-3 paid tool.

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 must compensate and does not. It never mentions search_window_start/end, topN, ayanamsa, latitude/longitude or the compact-mode fields, leaving the agent to rely on the raw schema for the core inputs.

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 and resource ('Auspicious-window scanner for short / daily travel'), which distinguishes it from the general muhurat family. It does not explicitly name the sibling astroway_vedic_muhurat_journey_long, though 'short / daily travel' implicitly contrasts with long journeys.

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?

No when-to-use or when-not-to-use guidance. The preferred nakshatras and days to avoid are domain result content, not instructions about when an agent should select this tool over journey_long or general_auspicious. The choice between the muhurat siblings is left entirely to inference.

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