Muhurat: Surgery (Shastrakarma)

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

Annotations already declare readOnly/idempotent/non-destructive; the description adds genuinely new context — that results are advisory only, that the polarity is inverted versus benefic muhurats, and the 50-credit Tier 3 cost. These are real behavioral facts not derivable from structured fields, though location defaults (0,0) are not disclosed.

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?

Three short sentences, each carrying distinct information (what it scans, the polarity rule, the advisory caveat), with the core purpose front-loaded. 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?

Output schema exists so return values needn't be explained, and the advisory framing is present, but for an 8-parameter electional tool the description never tells the agent that coordinates/timezone default to 0 and should be supplied, leaving a correctness-critical gap.

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?

Eight parameters with only 25% schema description coverage; the description only echoes the required search_window_start. topN, latitude, longitude, ayanamsaId, and search_window_end have no documentation anywhere, and the description does not compensate for that gap.

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?

States a specific verb and resource ('Auspicious-window scanner for elective surgery') and the surgery-specific scope separates it from the many sibling muhurat tools (marriage, business_start, travel, etc.). An agent can identify the resource without opening the schema.

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?

Gives real selection context: inverted polarity, Tue/Sat preferred, Sun/Mon/Thu/Fri avoided, advisory-only framing with medical scheduling taking precedence. It doesn't name an alternative sibling for non-surgical activities, so it stops short of a 5.

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