divine_get_muhurat_vehicle_purchase

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

Annotations already convey readOnly, openWorld, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds that the tool returns auspicious dates with muhurat details, but it does not disclose calculation source, timezone behavior, or other operational traits. This is acceptable given the strong annotations, but not exceptional.

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 two short, focused sentences with the purpose front-loaded and the output clarified in the second sentence. Every sentence earns its place with 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 simple read-only lookup with a full input schema and an output schema, the description plus structured metadata covers the essential invocation needs. It lacks sibling differentiation and a more precise definition of 'muhurat details', but those are not required for a correct call.

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 description mentions only 'month and location', while the nested schema already documents all required fields (month, year, place, lat, lon, tzone) and the optional lan field. The description adds little new parameter meaning beyond the schema, so a baseline 3 is appropriate.

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 uses a specific verb ('Get'), a specific resource ('Vehicle Purchase Muhurat'), and a clear scope ('for a given month and location'). The second sentence clarifies the output is auspicious dates with muhurat details. It doesn't explicitly distinguish itself from sibling muhurat tools like property purchase or business start, so it falls short of a 5.

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?

There is no guidance about when to use this tool versus the many sibling muhurat tools, nor any exclusions or prerequisites. Given the large sibling list with several similar muhurat operations, an agent is left to infer usage from the name alone.

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