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 that reading is sequential and carries across chapter boundaries and spans a multi-book Library, which is modest extra behavioral context, but it says nothing about pagination limits or return shape.

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 first sentence 'Gita Scroller.' and the second sentence restate the title almost verbatim, wasting space. The remaining clause then lists sibling capabilities ('daily verses, plans, search and verse lookup') that do not belong to this tool, so the text is repetitive and partially off-topic rather than front-loaded and purposeful.

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 four parameters fully documented in the schema and safety annotations present, the description only needs to add reading-flow context. It gestures at sequential reading across chapters but omits how passage navigation interacts with section/n/ref overrides and what a call returns, leaving it adequate but not complete for a 4-parameter tool.

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 schema already documents book, section, n and ref with examples, which sets the baseline at 3. The description adds no syntax or format detail beyond that ('a passage at a time' loosely gestures at n/section) so it does not raise the bar above 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 description conveys that this reads passages from a book one at a time ('read a passage at a time', 'whole books from the Library'), which gives a usable verb+resource. However, it muddies the identity by also listing adjacent capabilities ('daily verses, plans, search and verse lookup') that belong to sibling tools, so it does not cleanly distinguish itself from gita_get_reading, gita_get_chapter or gita_get_verse.

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?

'Follow next for the next passage; it carries on into the next chapter' is a hint about sequential scrolling, and 'whole books from the Library' hints at multi-book scope. But there is no explicit when-to-use or when-not-to-use guidance and no sibling is named as an alternative, leaving the agent to guess against eight other gita tools.

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