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

No annotations are provided, so the description carries the full behavioral burden. It does convey that the corpus is a fixed, curated catalogue (implying a read-only lookup), but is silent on result ordering, result limits/pagination, and what happens when query is omitted — notable since both parameters are optional and the tool would have to define a default.

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 actionable content is front-loaded in the first clause and the routing rule sits at the end, which is good. But the middle is a long author-by-author catalogue (Homer, Plato, Thucydides, Plutarch...) that could be compressed to a short statement of coverage; it aids relevance judgement but is padded well past what is needed.

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 two-optional-parameter search tool with no output schema and no annotations, the description covers scope, searchable fields and the sibling handoff, which is enough to invoke it correctly. Gaps are the return shape and the empty-query/no-results behaviour.

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 only 50% — 'query' has no schema description at all — and the description compensates by explaining that the free-text query matches across title, author, translator, blurb and group. That materially tells an agent how to phrase a query. It does not clarify how the free-text query interacts with the separate 'group' filter, which is the remaining ambiguity.

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 — search the library of ~1000 works — and enumerates the searchable fields (title, author, translator, blurb, group). The named handoff to read_work for in-text passage lookup makes it unambiguous versus the sibling that could be confused with it.

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?

Explicit routing rule: 'To find a passage inside a work, use read_work with find.' That is a concrete when-to-use-something-else condition. It doesn't address the other siblings (list_editions, get_passage, room) or say when a shelf search is unnecessary, so it stops short of full alternative coverage.

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