Muhurat — Property purchase / Griha Pravesh

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

Annotations already indicate readOnly, non-destructive, idempotent behavior. The description adds value by detailing preferred nakshatras, avoided days, cost (50 credits), and an example request. No contradictions with annotations; all traits are consistent and well-explained.

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 for purpose and guidelines, plus a line for auspicious details, group/cost metadata, and an example. Every sentence adds value, and the most critical info (purpose) is front-loaded.

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?

The tool has 7 parameters and no output schema. The description provides an incomplete parameter guide (missing ayanamsaId, topN) and does not describe the return format (e.g., list of windows). For a scanner tool, output structure is important; this gap reduces completeness.

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 includes an example request body that implies meaning for 5 of 7 parameters (search_window_start/end, lat/lon, timezoneOffset). However, ayanamsaId and topN are not mentioned, and schema coverage is 0%. With low coverage, the description should explain more; missing parameters reduce clarity.

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 'Auspicious-window scanner for purchasing or moving into property (Griha Pravesh)', with specific verb 'scanner' and resource 'property purchase/move'. It distinguishes from sibling muhurat tools by explicitly mentioning the activity, making the purpose unambiguous.

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 provides preferred nakshatras and avoided days (Sun/Tue/Sat), offering some guidance. However, it does not explicitly state when not to use this tool versus other muhurat tools, nor does it provide alternatives. Usage context is implied but not exhaustive.

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