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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuinely useful output context — that the chapter is returned in Sanskrit with transliteration and English — which matters since there is no output schema. It adds nothing about size, pagination, or error behavior for out-of-range chapters.

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 content-bearing line ('A whole chapter in Sanskrit with transliteration and English') is front-loaded and useful, but the lead brand name 'Gita Scroller' is filler and the long second sentence catalogs unrelated app features, violating the 'every sentence earns its place' standard.

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-parameter read tool with full annotation coverage and no output schema, the essential information (what content comes back) is present. What is missing is differentiation from the many sibling Gita retrieval tools and any handling note for invalid chapter numbers.

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% and the single 'chapter' parameter is fully documented with a 1–18 range, so the schema carries the semantics. The description only implies chapter selection via 'a whole chapter' and adds no format or edge-case detail beyond the schema.

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 name and title already convey 'a whole chapter in Sanskrit with transliteration and English,' and the first two sentences of the description largely restate that. The trailing clause about 'daily verses, plans, search and verse lookup; whole books from the Library, read a passage at a time' describes the app as a whole rather than this tool, so it does not sharpen the boundary against siblings like gita_get_verse, gita_get_reading, or gita_read_book.

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?

No statement of when to use this tool versus gita_get_verse (single verse), gita_get_reading (passage), or gita_read_book (whole book). The tagline even names adjacent capabilities (search, verse lookup, daily verses) without routing the agent to the tool that owns them, which could actively mislead selection.

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