divine_get_inauspicious_timings

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the description's job is lighter. It adds useful context by specifying that the tool returns unfavorable time windows and what those windows are, without contradicting 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?

Three sentences with distinct jobs: scope, output content, and use case. Every sentence earns its place and there is no filler or repetition.

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?

An output schema exists and safety annotations cover side effects, so the description need not explain return structure. It covers what the tool returns and why to use it; the main gap is not explicitly distinguishing it from the auspicious-timings sibling, but the name largely handles that.

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 nested PanchangInput schema provides detailed field descriptions for day, month, year, place, lat, lon, tzone, and optional language. The tool description only restates 'given date and location' and adds no parameter-level detail beyond what the schema already documents.

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: getting inauspicious timings for a date and location. It further names the exact returned categories (Rahu Kaal, Yamaganda, Gulika Kaal, Dur Muhurat), making it clearly distinguishable from the many sibling tools.

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?

Provides a clear use context ('avoiding inauspicious activities') but does not explicitly name the obvious alternative, divine_get_auspicious_timings, nor state when this tool should not be used. The differentiation is mostly implicit in the tool name.

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