divine_get_muhurat_do_ghati

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile is clear. The description adds modest context by stating the return content consists of auspicious timings and muhurat details, but it does not disclose any additional operational behavior such as timezone handling or result limits. No contradiction with annotations.

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?

The description is compact: two sentences with no filler. The first sentence front-loads the action and scope, and the second provides useful return-value context without redundancy.

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 read-only, idempotent lookup tool with a rich nested input schema and an output schema, this description is largely sufficient to invoke the tool correctly. The main gap is the lack of sibling differentiation for choosing this specific muhurat tool, but operational completeness is otherwise strong.

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?

The phrase 'date and location' loosely maps to the required day/month/year/place/lat/lon/tzone fields but adds little beyond the schema. The nested PanchangInput definition actually documents each field with examples, so the schema itself carries most of the parameter documentation burden. The description does not meaningfully explain language, timezone, or coordinate semantics beyond what the schema already provides.

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 clearly states the action 'Get' and the specific resource 'Do Ghati Muhurat' for a given date and location. It also notes that it returns auspicious timings and muhurat details. However, it does not explicitly distinguish itself from sibling muhurat tools such as divine_get_muhurat_hora or divine_get_muhurat_marriage.

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 gives only the general context of needing a date and location. It provides no guidance on when to use this tool versus other muhurat-related siblings, nor does it mention any exclusions or alternative tools.

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