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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds non-obvious behavior: content is read at call time from the house's own page, nothing is generated, the KJV Scripture is re-read from stored text, and it will report honestly when no page matches. Response format is not described, but an output schema exists.

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 sourcing and honesty guarantees are front-loaded and useful, but the description carries promotional padding ("why it still moves us", "Every hymn here sings of Jesus Christ; the worship room is where the family sings them together") that does not help selection or invocation.

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?

For a single-parameter read tool with rich annotations and an output schema, the description covers sourcing, provenance, and the no-match case, which is the main uncertainty an agent would have. It does not need to explain return values, so remaining gaps are minor.

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 title parameter is already documented as accepting a title or a line of it, with examples. The description merely echoes those examples, adding no new syntax, matching rules, or fallback behavior beyond what the schema states.

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 names a specific resource (a public-domain hymn) and enumerates exactly what is returned: author and date, backstory, lyrics, underlying Scripture, and significance. This is clearly distinguishable from siblings like worship_now, prayers, or saint_of_the_day without opening any 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?

It gives concrete triggering phrasings ("the story of Amazing Grace", "words of It Is Well With My Soul", "a hymn about trusting Jesus") so an agent can match user intent, and it points to the worship room for the communal-singing use case. It stops short of explicitly naming a sibling to use instead or stating when not to call it.

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