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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds meaningful provenance and fallback behavior beyond that: content is read at call time from a specific page, the prose is the house's, Scripture is re-read from stored KJV text, nothing is generated, and it is "honest when no page matches" — useful behavioral context.

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?

It is front-loaded correctly (purpose first, provenance and fallback after), but the prose is long and includes example questions and a closing theological aside ("All Scripture testifies of Christ (John 5:39)") that does not help an agent select or invoke the tool.

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?

An output schema exists, so return values need not be spelled out, and the description supplies scope, provenance, and empty-match behavior. It is complete enough to call correctly, with the only gap being the lack of sibling comparisons.

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% for the single 'topic' parameter, so the baseline is 3. The description adds scope ('about three hundred topics') and a list of examples that illustrate acceptable values, but adds no syntax or format detail beyond the schema.

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 and resource: it returns Bible verses on one of ~300 topics, each with a plain-language meaning, drawn from the house's own pages. The topic-question framing ("what does the Bible say about shame") makes it clearly distinct from raw-search siblings like scripture_search or verses_for without opening either schema.

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?

Usage is implied by the example user questions and the topic-based framing, which gives decent contextual signals for when this tool fits. However, it never explicitly contrasts itself with alternatives like verses_for, scripture_search, or scripture_context, nor states when-not to use it, so the routing guidance remains inferential.

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