get_muhurta

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

No annotations are provided, so the description carries the behavioral disclosure burden. It explains the JSON return, fields included, the derived-timezone behavior, and the system calculation options. It does not mention error behavior or invalid-input handling, but the output schema and parameter guidance cover most operational context.

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 more than a sentence or two but remains well-organized: purpose, use case, output fields, then args. The exhaustive field list adds length but is valuable for an agent deciding whether this tool returns the needed timing data.

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?

Given no annotations, six parameters, and an output schema that likely documents return structure, this description covers purpose, usage, output scope, and parameter semantics. An agent has enough context to select and call the tool correctly.

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 0%, yet the description independently documents all main parameters: date format, city-or-coordinates alternative, timezone derivation, and system enum values with default. This fully compensates for the lack of schema descriptions and adds meaningful usage meaning.

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?

State a specific verb ('Returns'), resource ('auspicious and inauspicious time windows'), and scope ('for a date and city'). It also differentiates itself from get_panchangam by saying it is lighter and oriented toward quick queries, so an agent can distinguish sibling tools without opening schemas.

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?

Explicitly says to use it for quick 'is this a good time?' queries and contrasts it with get_panchangam. It does not enumerate when-not-to-use conditions or mention other relevant siblings like find_muhurta, but the guidance is clear enough for basic routing.

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