Muhurat — Education start (Vidyarambha)

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it's a 'scanner' of windows, which is consistent. No additional behavioral quirks (e.g., rate limits, response format) are disclosed, but the safety profile is covered by 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 short (4 lines), includes an example, and front-loads the purpose. Every sentence adds value, though it could be more structured (e.g., bullet list for parameters).

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 7 parameters, no output schema, and annotations present, the description covers domain context (Vedic muhurat), preferred timings, and provides an example. However, it lacks full parameter descriptions and output expectations, leaving gaps for a complete understanding.

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%. The description only gives an example request body covering 5 of 7 parameters (search_window_start, search_window_end, latitude, longitude, timezoneOffset). It does not explain ayanamsaId or topN (which controls max results). Parameter meaning is poorly compensated.

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 title and description clearly state the tool finds auspicious windows for starting formal education (Vidyarambha). It lists preferred nakshatras and days to avoid, distinguishing it from other muhurat tools by name, but does not explicitly differentiate from 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 criteria (preferred nakshatras, avoid Sun/Tue/Sat) for when the scanner is applicable, implying use for education start ceremonies. However, it does not provide explicit when-not-to-use cases or compare with other vedic_muhurat_ tools.

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