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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds genuinely useful context beyond that: which edition each Enoch/Jubilees alias resolves to, that background essays append a URL, and that Apocrypha results carry canon_status and disclaimer_url. It does not describe pagination or size limits, but the alias-resolution disclosure is substantive.

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 purpose is front-loaded, which is good, but the body is a dense run-on enumeration of alias-to-edition mappings (charles-1917, charles-1913, morfill-1896, odeberg-1928) that is hard to scan. The content is relevant but the structure is a wall of clauses rather than an organized list.

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?

Annotations cover the safety profile and an output schema exists, so return-value detail is a bonus rather than a requirement. However, for a 4-parameter read tool with zero schema descriptions, the missing semantics of verse and reference leave an agent guessing; adding one clause on those would make it complete.

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 0%, so the description carries the full burden. It explains the book parameter well (names vs OSIS codes, aliases) and hints that chapter returns a whole chapter's verse text, but the verse and reference parameters - including how reference differs from book+chapter+verse - are entirely unexplained.

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 states a specific verb and resource - retrieves King James text for a book name or OSIS code - and even enumerates the alias forms it accepts. It scopes itself to KJV text, which implicitly separates it from compare_translations, but it never names any sibling tool explicitly.

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 get_verse or compare_translations, both of which sit in the sibling list. The reader can infer it is the KJV single-translation lookup, but no explicit condition or alternative is given.

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