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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, covering the safety profile. The description adds useful continuation behavior ('carries on into the next chapter'), but says nothing about pagination, ordering, or what a passage contains beyond what the schema implies.

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 opening is front-loaded, but the second sentence is a general overview of the whole Gurbani server rather than this tool, mixing unrelated features ('plans, search, Ang and shabad lookup') into a definition that should focus on reading a book passage by passage.

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?

As a read-only tool with no output schema and full schema coverage of its 4 params, the minimum viable information is present. Still, it never explains ordering across chapters/sections or how ref interacts with section for continuation, which would help an agent drive sequential reads.

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 book, section, n, and ref are already fully documented in the schema, including the ref override semantics. The description adds no parameter-level detail, 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 final clause 'whole books from the Library, read a passage at a time' does convey the specific verb+resource, and the title clarifies sequential passage reading. However, it is tangled with a server-level overview ('daily shabad, plans, search, Ang and shabad lookup') rather than a crisp statement of this tool's function, and it never distinguishes itself from gurbani_get_reading or gurbani_get_today.

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' implies sequential reading use, but there is no explicit when-to-use versus the many sibling reading tools (gurbani_get_reading, gurbani_get_ang, gurbani_get_card). An agent must infer which tool to pick with no routing guidance.

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