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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the read-only safety profile is fully covered by structured data. The description adds nothing behavioral beyond that – no note on whether the list is paginated, static catalog vs. date-dependent, or how large the response is.

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?

It is short and the resource is front-loaded, but the second sentence is a catch-all family blurb that mixes in other tools' functions, so it does not fully earn its place and creates ambiguity rather than trimming it.

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-param browse tool with no output schema, the description should at least clarify what the returned list contains (curated reading plans vs. today's reading) and how it relates to gurbani_get_today/gurbani_list_books. Instead it conflates the whole family's capabilities, leaving the agent unsure what this call actually yields.

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 no parameters and the schema is empty, so there is nothing for the description to clarify. Per the baseline for a zero-parameter tool, a 4 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 first two sentences ('Scroll the Gurbani. All curated daily readings and plans.') essentially restate the title and name, giving no specific verb beyond the vague 'Scroll'. The remaining clause then lists capabilities belonging to sibling tools (daily shabad, search, Ang and shabad lookup, whole books, read a passage), so it neither pins down this tool's resource nor distinguishes it from gurbani_get_reading, gurbani_list_books, or gurbani_search_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 statement of when to use this tool versus gurbani_get_today, gurbani_list_books, or gurbani_search_readings. Worse, by enumerating sibling capabilities ('search', 'Ang and shabad lookup', 'read a passage at a time') it implies this tool covers those jobs, which is the opposite of routing guidance.

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