Muhurat — Surgery (Shastrakarma)

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds the cost (50 credits, Tier 3) and group (Vedic), and reinforces the advisory nature. This provides useful behavioral context beyond the annotations.

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 very concise: four sentences plus meta-data lines and an example. It front-loads the purpose and each sentence adds necessary information without redundancy. No wasted words.

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 7 parameters and no output schema, the description provides a good overview of purpose and usage context but does not describe the return format or explain all parameters. An AI agent might infer the output from 'auspicious-window scanner', but explicit details would improve 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?

Schema description coverage is 0%, so the description should compensate. It includes an example request body that demonstrates some parameters (search_window_start, search_window_end, latitude, longitude, timezoneOffset) but does not explain all 7 parameters, especially ayanamsaId and topN. The example adds some value but is insufficient for full parameter understanding.

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 it is an 'Auspicious-window scanner for elective surgery', using a specific verb and resource. It distinguishes itself from sibling muhurat tools by specifying 'surgery' and explains the inverted polarity for day preferences.

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 clear context for use, including that it is for elective surgery and that the output is advisory with medical scheduling taking precedence. However, it does not explicitly mention when not to use or compare with alternatives among the sibling muhurat tools.

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