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

Adds real behavior beyond readOnlyHint/openWorldHint: it caps matches, defines the return shape (references with one line of English and links), and advises Greek input may be accented or not. Does not state pagination or whether limit above 10 is rejected, but is informative for a read-only search.

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 sentences, front-loaded with what is searched and what is returned, then the next-step routing and Greek note. No filler.

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?

Covers purpose, result shape, and next step well enough for a simple 3-parameter search with no output schema. Could state the default limit or book-scope precedence, but nothing critical is missing.

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%, so the schema already explains query, book, and limit. The description adds only the Greek accent tolerance, which is modest extra meaning. Baseline 3 is 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 (finds passages) plus the resource scope (library or one book) and match condition (English translation or original text contains query). A reader can distinguish it from get_passage, lookup_word, and list_books without opening a 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?

Explicitly routes the agent onward: 'call get_passage to read a match word by word,' which distinguishes this discovery tool from the passage-reading sibling. No explicit statement of when not to use it versus lookup_word, but the context is clear.

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