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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so safety and determinism are covered. The description adds that results derive from VedicDost's software plus classical nakshatra/tithi/weekday rules, which is useful provenance, but it doesn't explain result volume, timezone/place effects, or defaults 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 sentences, front-loaded with the verb and resource, then the methodological basis, then usage examples. Slightly dense but every clause carries information; no 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?

For a 7-parameter read-only query tool with no output schema, the definition covers purpose, method, and typical queries adequately. The main omission is any hint of the response shape (dates plus reasons/links) and how place vs. coordinates resolve.

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 57%, so the description's explicit enumeration of event categories (marriage, griha pravesh, vehicle, business) meaningfully clarifies the required enum. It says nothing about latitude/longitude pairing with place or how days interacts with from, leaving the remaining gap unaddressed.

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 (finds) and resource (auspicious muhurat dates), enumerates the supported event types, and gives the calendrical basis (nakshatra, tithi, weekday). It is clearly distinct from siblings like get_panchang or match_kundli.

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?

Provides concrete example queries ("shubh muhurat for marriage in 2027", "griha pravesh dates next month") that anchor when to use it, plus a date-range constraint. It doesn't explicitly say when to prefer a sibling such as life_event_timing, but the use context is clear.

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