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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context beyond that – no mention of pagination, catalog scope, result ordering, or what 'the Library' means operationally. It only restates domain framing.

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 duplicating the title verbatim, then appends a run-on clause listing unrelated Gurbani capabilities that do not belong to a book-listing tool. Substantial content is wasted rather than front-loading a clean statement of what the tool returns.

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 zero-parameter read-only listing with rich annotations, the description is minimally adequate but not complete. It doesn't say what the listing returns or how to act on it, and the extra Gurbani clause muddies rather than fills the gap.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to clarify. Baseline of 4 applies; the description neither adds nor detracts from parameter understanding.

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 first sentence names the resource (whole books in the Library that can be read a passage at a time), so an agent can infer this lists available books. However the verb 'list' is never stated, and the second sentence mixes in unrelated Gurbani features (daily shabad, plans, search, Ang and shabad lookup) that don't describe this tool. It also fails to distinguish itself from siblings read_book or list_readings.

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 indication of when to call this tool versus the many siblings (list_readings, read_book, get_reading). The description offers no trigger condition, prerequisite, or exclusion, leaving the agent to guess from the name alone.

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