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

Annotations already indicate readOnlyHint=true, so the description focuses on additional behavioral details: the output includes a url for opening the verse in the app, and the behavior when verse parameters are omitted (whole chapter). No contradictions with annotations.

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?

Three concise sentences each serve a purpose: first defines the action, second explains parameter modes, third advises on output url. No redundancy or unnecessary information.

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?

Without an output schema, the description covers key return value (url). It addresses all input aspects: book name format, verse parameter modes, default version. Complete for a retrieval tool.

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 description adds significant context beyond the schema: it explains the logical relationship between verseFrom and verseTo (single, range, chapter) and the default version (THAKJV). Since schema coverage is 100%, the description elevates understanding beyond baseline.

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 description clearly states it retrieves Bible verses by reference, specifying three modes (single verse, range, whole chapter). It distinguishes from sibling tools like search_scripture and get_daily_verse by focusing on exact references.

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 description explains that English book names must be used and outlines the three usage modes. It implies when to use this tool (exact reference) versus siblings (search, daily verse) but does not explicitly state when not to use or provide direct alternatives.

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