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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description adds no behavioral context beyond that – no mention of auth needs, computation cost, latency, or how missing location inputs are resolved, and its field enumeration duplicates the 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?

A single front-loaded sentence that leads with the return payload. It is dense but not padded, though the long comma-chain of fields could be trimmed since an output schema already exists.

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?

For an 8-parameter tool with nested objects, an anyOf location requirement, and a sibling that covers natal panchanga, the description leaves critical invocation details (how to supply location, when natal is required) unexplained. It compensates only by affirming that natal balas are optional.

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 only 38% across 8 parameters with nested objects and an anyOf place-vs-coordinates constraint. The description clarifies only that the natal bala input is optional; it says nothing about date format, place vs. explicit latitude/longitude/timezone selection, the language enum, or timezoneOffset behavior.

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 enumerates what the tool returns (five limbs, Rahu Kaal, Yamaganda, Gulika, Choghadiya, Horas, festival flags, optional balas), so an agent knows the resource well. However, it never names or distinguishes itself from the sibling get_natal_panchanga, so the differentiation dimension is missing.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives such as get_natal_panchanga or find_muhurta. The agent must infer the use case entirely from the tool name and returned-field list.

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