Muhurat — Investment / Dhana Sthapana

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

Annotations already indicate the tool is read-only and idempotent. The description adds that it scans for auspicious windows and mentions cost (50 credits). However, it does not describe the output format or any other behavioral traits beyond the annotations, which is a gap given the absence of an output schema.

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 concise, with the purpose front-loaded in the first sentence. It includes relevant details (nakshatras, avoid days, group, cost) and an example. No redundant information, though the example could be separated but is not detrimental.

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 the tool has 7 parameters, no output schema, and a specialized domain, the description is incomplete. It lacks parameter explanations, output expectations, and behavioral details. The agent would need additional context to use the tool effectively, especially for parameters not in the example.

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 input schema has 0% description coverage, so the description must compensate but only provides an example request body with some parameters. It does not explain the meaning of parameters like ayanamsaId or topN, nor the allowed values or constraints. The example gives format hints but lacks semantic depth.

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 tool's purpose as an auspicious-window scanner for major investments and financial commitments, listing examples like deposits, share/bond purchase, and lending. It includes specific nakshatras and days to avoid, and the title 'Investment/Dhana Sthapana' further distinguishes it from sibling muhurat tools for other activities.

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 specifies the use case ('major investments and financial commitments') and provides celestial guidelines (preferred nakshatras, avoid days). However, it does not explicitly state when not to use this tool or name alternative tools for other muhurat purposes, though the domain is clear from context and sibling tool names.

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