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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so safety is covered. The description does add one genuine behavioral detail: 'it carries on into the next chapter,' useful for a scroller-style read. However, it says nothing about rate limits, return format, or how the ref/n/section interplay behaves at boundaries.

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 opens by restating the title verbatim ('Follow next for the next passage; it carries on into the next chapter') and then lists features that belong to other tools, which is noise rather than front-loaded signal for this tool. The only tool-relevant phrase is buried at the end.

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 4-parameter read tool with no output schema, the description should clarify how book/section/n/ref compose and what a call returns (a passage card?), especially given its scroller/continuation framing. Instead it omits any of that and spends its length on app marketing and sibling features.

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 all four parameters (book, section, n, ref) are fully documented in the schema, including the precedence rule that ref overrides section and n. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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 signals a read operation ('read a passage at a time') over a book/passage resource, but the first two sentences are app-flavored ('Gita Scroller', 'Follow next') rather than stating the action. It also lists unrelated capabilities (daily verses, plans, search, verse lookup) that belong to sibling tools, muddying what this specific tool does. The verb+resource pair is discernible but not crisply stated.

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?

There is no guidance on when to use this tool versus clear siblings like gita_get_reading, gita_get_verse, or gita_get_chapter. The 'read a passage at a time' hint is the only implicit usage cue, and no alternatives or exclusions are named.

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