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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so safety is covered. The only added behavioral fragment is 'read a passage at a time', which is a thin hint about consumption granularity and could equally describe gurbani_read_book. It adds little beyond the structured fields.

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 a fragment run-on: 'Gurbani: daily shabad, plans, search, Ang and shabad lookup; whole books from the Library, read a passage at a time.' Ideas are dumped without hierarchy and the second sentence does not earn its place because it describes other tools' work rather than this one's.

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 list tool with annotations already carrying the safety profile and no output schema, the description only needs to convey what is returned. It gestures at 'all curated daily readings and plans', but the trailing sibling-capability list muddies the scope and never clarifies the return shape.

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, so there is nothing for the description to disambiguate at the argument level; the baseline for a zero-param tool is 4.

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 plus title indicate a listing of all curated daily readings and plans, which is a recognizable verb+resource. However, the second sentence drifts into 'daily shabad, plans, search, Ang and shabad lookup; whole books from the Library', which describes capabilities owned by sibling tools (gurbani_get_shabad, gurbani_search_readings, gurbani_read_book). This blurs rather than sharpens what this specific tool does.

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 the many gurbani_* siblings. Worse, it names 'search' and 'Ang and shabad lookup' without routing guidance, so an agent may pick this tool for a search or a shabad lookup that belongs to gurbani_search_readings or gurbani_get_shabad.

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