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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description adds real value by disclosing that the result is purely weekday-derived (deterministic, no ephemeris lookup needed) and that it includes a remedy item and week table; it does not, however, discuss response shape or any caveats of the traditional rule.

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?

Front-loaded with the core meaning, then the lookup table, then the scoping constraint. The parenthetical weekday mapping is long but earns its space since it is the tool's entire logic; the endpoint and cost metadata is boilerplate that the agent could get elsewhere.

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?

For a single-required-parameter, read-only lookup with an output schema, this is essentially complete: the agent knows the input, the computation basis, and the categories of returned content. Only the relationship to the muhurat/travel siblings is left unaddressed.

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 coverage is 100%, so the baseline is 3. The description's note that only the weekday matters reinforces the `date` field but largely duplicates what the schema already states ('Its weekday decides the direction'), and it says nothing about the `fields` or `precision` compaction parameters.

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 defines what 'Disha Shool' actually is — the direction to avoid for travel on a given weekday — plus the remedy item and week table, which an agent could not infer from the opaque name. It enumerates the exact weekday-to-direction mapping, making the tool's output identifiable without opening the schema, and it is clearly separable from the other panchang siblings (tithi, hora, choghadia).

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?

It says 'Only the weekday is used,' which usefully tells the agent that no time, place, or birth data is required — an important contrast with most panchang tools that need location. However, it never states when to reach for this versus astroway_vedic_muhurat_journey_long or astroway_vedic_muhurat_travel, nor any exclusions, so routing is left to inference.

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