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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds useful behavioral detail by specifying the exact return content: Sanskrit name, Western equivalent, sidereal date range, symbol, governing Aditya, and personality characteristics. It does not cover every edge case, but for a single-record read the behavior is transparent enough.

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 one tight sentence that front-loads the core purpose and then enumerates the useful return fields. There is no filler, repetition of the tool title, or unrelated background.

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 a single-item read-only lookup, the description, combined with the fully documented schema and read-only annotations, gives an agent everything needed to select and invoke it correctly: the exact ID values are in the schema, all optional parameters are described, and the return field list makes the output predictable without an output schema.

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 100%, so the parameters are already fully documented. The description adds only minor context such as 'Vedic ID slug' and 'Sanskrit name', but it does not meaningfully expand on the lang fallback or compact shape beyond what the schema already explains. The schema-heavy baseline of 3 is appropriate.

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 states a specific verb ('Get'), a precise resource ('a single rashi ... by its Vedic ID slug'), and lists the main returned fields. This clearly distinguishes it from the plural sibling get_vedic_astrology_rashis and from other detail endpoints like nakshatras_id.

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 makes clear this is for single-item lookup by an ID, which implies use when a specific rashi is already known. It does not explicitly name get_vedic_astrology_rashis as the alternative for listing all rashis, but the singular and ID-focused wording is clear enough context without explicit exclusions.

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