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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond that — no statement of what the call returns, ordering, or whether results are cached/static. It is not contradictory, just empty.

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 text is repetitive and poorly front-loaded: 'Scroll the Gurbani' is restated twice and followed by a run-on inventory of unrelated app features. The core purpose is never stated in a leading, scannable clause.

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, no-output-schema tool the description should at minimum state that it returns the list of available books and how that differs from gurbani_list_readings. Instead it leaves the return content and the sibling boundary entirely implicit, which is inadequate given the dense cluster of gurbani_* tools.

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, which is the baseline-4 case. The empty schema is consistent with a simple catalogue-listing call, and the description neither helps nor harms here.

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 never states a verb like 'list' or 'return'; it opens with the marketing phrase 'Scroll the Gurbani' and then vaguely describes 'the whole books in the Library that can be read a passage at a time.' An agent has to infer from the tool name alone that this returns the catalogue of books, and nothing distinguishes it from siblings like gurbani_list_readings or gurbani_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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The trailing sentence lumps together unrelated capabilities ('daily shabad, plans, search, Ang and shabad lookup') rather than telling the agent when this specific tool is the right call versus gurbani_list_readings.

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