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

Annotations already establish read-only, idempotent, non-destructive behavior, so the bar is lower, yet the description adds real constraints: public-domain English translations only, translation and licence always reported, and numbering conventions per tradition. It stops short of describing pagination or how multi-verse ranges are bounded beyond the schema's 'up to 12 verses.'

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?

Front-loaded with the primary lookup behavior, then constraints, then invocation. Dense but every sentence carries information; the parenthetical example lists are slightly repetitive of the schema examples but not wasteful.

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?

With no output schema, the description steps in to say results carry translation and licence, and it covers traditions, language limits, and numbering caveats. Remaining gaps are minor: no mention of result count limits for topic searches or empty-result behavior.

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 coverage is 100% so the baseline is 3, but the description earns more by clarifying the reference parameter's tradition-specific numbering (Gita/Dhammapada/Tao Te Ching/Analects/Zhuangzi are passage-numbered, not chapter:verse) and by noting reference overrides topic — semantic detail the schema does not carry.

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 pair — looks up a verse by reference or finds one on a topic — and enumerates the traditions and reference formats, so the agent knows exactly what the tool returns. It does not, however, distinguish itself from the sibling search_quotes, which plausibly overlaps in the 'find text by theme' space.

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?

Gives clear invocation guidance: 'Give a reference or a topic,' explains that reference takes precedence over topic, and warns that non-Bible traditions are numbered by passage so a chapter should be requested. No exclusions or named alternatives against siblings, which caps it below 5.

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