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 covered. The description adds genuinely useful context beyond that — the reading is text-sourced ('no AI writing') and access is tiered ('free view; full Rs 51 reading') — implying the default response is a partial/preview output, but it does not specify what that preview contains or any error behavior.

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?

Front-loads the core purpose before the long topic list. The topic enumeration is dense but justified since it enumerates the enum values; the closing pricing sentence is a separate, useful clause rather than padding.

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?

With 9 parameters, 5 required, no output schema and no nested objects, the description should carry more of the return-value burden. It hints that the default is a limited free view versus a fuller paid reading, but never states what the reading actually returns or how the two tiers differ, leaving a meaningful 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?

Schema coverage is 78%, so most parameters are already documented. The description's topic list maps natural-language questions onto the topic enum values, which is mildly helpful, but it adds no syntax or format detail beyond the schema for date, time, lat/long or timezone.

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 — a 'Granth-based reading for a life question' — and names its sources (BPHS, Phaladeepika) plus a concrete list of question types. It does not explicitly distinguish itself from siblings like janam_kundali or kundali_milan, and in fact claims 'a general kundali reading' as one of its topics, which blurs the boundary.

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 enumerated topics (ex back, toxic boss, career pivot, property timing, etc.) give clear implicit context for when this tool applies. However there are no exclusions and no routing to alternatives, so an agent cannot tell when to prefer janam_kundali or kundali_milan over this.

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