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

Annotations already establish the safe, read-only, idempotent, closed-world profile, so the description is free to add value elsewhere and does: it discloses the exact return payload (Sanskrit, transliteration, two translations, chapter.verse) and an operational rule ("Always cite the reference"). It does not mention ranking, relevance cutoffs, or empty-result behavior, keeping it out of the 5 range.

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-loaded with the trigger condition, then search mechanics, then query-format guidance, then the return contract. The parenthetical situation list is long but earns its place by widening recall; no sentence is filler.

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 no output schema, the description must carry the return contract, and it does precisely (fields plus reference format). Combined with the trigger guidance and query-language rule, an agent has everything needed to invoke this correctly.

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 baseline is 3, but the description genuinely adds semantics the schema lacks: the query should be written in English describing the feeling even when the user wrote Hindi or Hinglish, with worked examples. That materially changes how an agent formulates the required parameter.

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 (semantic search) and resource (all 700 verses of the Bhagavad Gita), and the example queries plus the chapter.verse return make it unmistakable against siblings like get_gita_verse or search_mahabharata.

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?

Opens with an explicit trigger ("Use when the user asks for guidance, comfort, or a teaching on any life situation...") and enumerates the relevant situations, giving strong when-to-use guidance. It stops short of naming the sibling alternative (e.g. get_gita_verse for a specific known verse), so it misses the top of the range.

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