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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description still adds real value: content is read at call time from the house's own page, wording is the house's, Scripture is re-read from the stored King James text, and nothing is generated. The no-match behavior is disclosed. It stops short of describing response shape or caching/latency traits.

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 topic enumeration and provenance ('the words are the house's, the Scripture is re-read from the stored King James text, nothing is generated') are load-bearing, but the closing devotional line about Jesus Christ does not help tool selection, and the opening 'One of the house's...' delays the core purpose.

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 an output schema present, return values need no explanation, and the description supplies the provenance, honesty-on-miss, and content-scope context an agent needs. Only the choice against near-duplicate siblings is left unaddressed.

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% and the single 'topic' parameter already documents its examples and length bounds, so the schema carries the load. The description's topic list and example questions reinforce but do not add format or matching semantics beyond what the schema provides, making the 3 baseline appropriate.

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 identifies the resource clearly (the house's 'What Christians Believe' pages, short and full) and enumerates the topics it covers, and it distinguishes itself from siblings like what_the_bible_says_about by naming its own page and provenance. It never leads with a clean verb like 'retrieve/read', so the action must be inferred from 'Read at call time', which softens the clarity.

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?

It implies the use case via example queries ('what is grace', 'what do Christians mean by salvation'), which helps an agent match user phrasing. But it never states when to prefer this over close siblings such as what_the_bible_says_about, the_gospel, or christianity_and_other_faiths, nor any exclusion conditions beyond 'Honest when no page matches'.

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