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 by structured data. The description adds that results include transliteration and English, a useful payload detail, but says nothing about pagination, size of a whole shabad, or failure modes for an invalid id.

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 first two sentences are tight and front-load the essential information. The third sentence is a comma-spliced catalog of the whole Gurbani family that adds no actionable content for this specific tool and dilutes the signal.

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 one-parameter, fully annotated read tool with no output schema, the description conveys what comes back (transliteration and English), which is the main thing an agent needs. It is adequate but stops short of clarifying its position among the four other Gurbani retrieval 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?

With 100% schema description coverage and a single documented parameter, the schema already carries the semantics; the description only echoes 'by BaniDB id'. Baseline 3 is appropriate since no format or provenance detail is added beyond what the schema states.

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?

States a specific verb+resource ('a whole shabad'), the identifier domain ('by BaniDB id'), and the payload ('with transliteration and English'), which is enough to distinguish it from gurbani_search_readings or gurbani_list_books. However it never disambiguates from close siblings like gurbani_get_ang, gurbani_get_reading, or gurbani_read_book, which also retrieve Gurbani text.

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?

The trailing 'Gurbani: daily shabad, plans, search, Ang and shabad lookup; whole books from the Library' sentence is a family/taxonomy listing, not usage guidance for this tool. It offers no condition for choosing this over gurbani_get_ang or gurbani_read_book, and no prerequisites.

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