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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond them: the birth city is looked up in memory and not persisted, and there is a scope limitation on the kinds of claims the reading may make. It stops short of describing what the reading output contains.

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?

Two dense sentences with the usage triggers front-loaded and the exclusions trailing; nothing is wasted. Slightly run-on, but every clause carries routing or constraint information.

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?

Usage, exclusions and privacy behavior are well covered, but with no output schema the description should carry the return-value burden and says nothing about what a reading contains (sections, length, format). That is the main missing piece for a tool of this complexity.

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 coverage is 100%, so the baseline is 3. The description reinforces the placeName semantics ('city text only ... looked up in memory') which the schema already states, but adds nothing about the date parameter, whose schema label ('YYYY-MM-DD birth date') is the most ambiguity-prone part of the call.

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: produce a daily/weekly Vedic astrology reading (gochar/transits) from the user's birth details. It is readily distinguishable from siblings like naksha_chart, naksha_compatibility, naksha_mangal_dosha and naksha_sade_sati, which cover different astrological scopes.

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?

Explicit when-to-use triggers are given (today/this week astrologically, the Hindi phrase 'aaj ka din kaisa rahega', current transits/gochar, daily reading from birth details) plus explicit exclusions ('do not use for general panchang or rahu kaal with no birth details'). It also states a content guardrail about not making deterministic health/death/finance claims.

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