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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds the useful behavioral fact that the result includes transliteration and English, but says nothing about invalid-id behavior or response size. Adequate with annotations, not rich.

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 core statement ('A whole shabad by BaniDB id, with transliteration and English') is well front-loaded. However, it largely duplicates the title, and the second half is app-level boilerplate listing unrelated features ('daily shabad, plans, search, Ang and shabad lookup; whole books from the Library'), which does not earn its place in this tool's description.

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?

A one-parameter read-only lookup with full schema coverage likely has an output schema absent, so the description's note that it returns transliteration and English is a meaningful completion. Combined with annotations covering safety and idempotency, an agent has enough to call it correctly, though the sibling-boundary information remains thin.

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?

Schema description coverage is 100% for the single 'id' parameter, so the schema fully documents it and a baseline of 3 applies. The description repeats the 'BaniDB id' notion but adds no format, range, or example beyond the schema text.

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 title/description states a specific verb and resource: fetch a whole shabad by BaniDB id with transliteration and English. It is clear what the tool returns, but it never names or distinguishes itself from near siblings such as gurbani_get_ang, gurbani_get_reading, or gurbani_search_readings, so the agent must infer the boundary.

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 explicit when-to-use or when-not-to-use guidance. The phrase 'read a passage at a time' hints at a contrast with passage-level tools, but no alternative is named and no condition for selecting this tool over gurbani_get_ang or gurbani_search_readings is given. The trailing list ('daily shabad, plans, search, Ang and shabad lookup') enumerates other app capabilities rather than routing guidance for this tool.

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