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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds substantially beyond that: it discloses the result cap (top 10), that values are pre-computed at seed time, the embedding model and dimensionality, cosine similarity as the metric, and the score (0..1) and rank (1..10) ranges. The 'semantic neighbors, not curated parallels' caveat is a genuine behavioral disclosure that prevents misuse.

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?

Two tight sentences with the core behavior front-loaded and the caveat placed strategically at the end. The embedding-model/dimension detail ('text-embedding-3-large (3072-d)') is mildly implementation-flavored, but it supports interpretation of the similarity scores.

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 read-only lookup with a full output schema, the description supplies everything needed: what is returned, how many results, how they are scored and ranked, and the crucial caveat that these are not curated parallels. Return-format explanation is correctly delegated to the output schema.

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% with three required parameters (book_code, chapter, verse) each documented, so the schema carries the parameter burden. The description adds no additional semantics about parameter format, valid book codes, or out-of-range behavior, making the baseline 3 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?

States a specific verb and resource: returns the 10 Urantia paragraphs whose embeddings are nearest to the Bible chunk containing the given verse. The embedding/similarity framing clearly distinguishes it from siblings like bible.verse (plain verse lookup) or search.semantic (generic search).

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 closing line 'These are semantic neighbors, not a curated list of parallels' gives a clear interpretive caveat that shapes how an agent should use the results. It does not, however, name an explicit alternative or state when-not to use it versus search.semantic or bible.verse, so it falls short of full routing guidance.

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