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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description instead spends its budget on non-obvious behavior: the invisible `listed`-false exclusion and the caveat that the returned `image` is the raw publisher value, not the computed display cover. Both are facts an agent could not infer from schema or annotations.

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?

Front-loaded with purpose, then usage condition, then exclusions — the right order. The image-cover caveat runs three lines and could be tightened, and a few Args entries restate names the schema already shows, but nothing is 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?

For a read-only, five-parameter, zero-required browse tool with an output schema already documenting return shape, this covers everything an agent needs: intent, filtering semantics, pagination, sort values, and the one misleading return field.

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 0%, so the description must carry all parameter meaning and it does: it names which fields `search` matches (name, description, publisher name), gives language format examples including region/script forms, enumerates the ordering values with `-downloads` as default, and states the 1–100 limit range with default 20.

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?

Opens with a specific verb+resource ('Browse published Bible verse collections') and immediately names the three supported operations (keyword search, language filter, popularity sort). The 'published' qualifier scopes it against the sibling get_collection_detail, which it names explicitly.

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?

Gives a concrete when-to-use with the user's likely phrasing ('verses to memorize on a theme (e.g. hope, anxiety, forgiveness) or a ready-made memory list'). It also states the exclusion condition — collections with `listed` false are not returned — and points to get_collection_detail as the alternative that still opens them by id.

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