divine_get_muhurat_foundation_laying

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

Annotations already declare this a read-only, idempotent, non-destructive operation. The description adds that the result is a list of auspicious dates with muhurat details, which is useful but modest; it does not disclose edge cases, calculation dependencies, or how location/timezone affect the result.

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 tight, front-loaded sentences with no filler. The first states the operation and scope; the second states the output shape. Every word earns its place.

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 lookup with a detailed input schema and an output schema present, the description provides enough for correct invocation. Minor omissions such as language selection and explicit sibling differentiation do not block usage.

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 identifies month and location as the core inputs, aligning with the schema's required month, year, place, lat, lon, and tzone. It adds only selection-level meaning, not deeper guidance on how lat/lon/tzone are used, though the nested schema does document each field individually.

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 names the exact resource ('Foundation Laying (Bhoomi Pujan) Muhurat'), uses the specific verb 'Get', and scopes the operation to month and location. This clearly differentiates it from the many other muhurat and astrology siblings.

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 clear context—month and location—and states what is returned, so the intended use case is inferable. However, it does not explicitly say when to prefer this tool over related siblings like marriage, house-entering, or business-start muhurat tools, nor does it state any exclusions.

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