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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, non-open-world), so the description is free to add behavior instead of repeating it. It does: unlisted collections are silently excluded from results, and each result's `image` is the raw stored publisher URL (possibly null) rather than the computed display image. That field-semantics disclosure is genuinely useful, though no pagination edge behavior or result-size limits are discussed.

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?

Purpose is front-loaded, followed by usage, exclusions, result semantics, then an Args block — a sensible order with no wasted sentences. The image/cover paragraph is the longest and slightly verbose for its value, but it is not 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?

All five optional parameters are documented despite 0% schema coverage, annotations already carry the safety profile, and an output schema exists so return values needn't be spelled out — the extra note on the `image` field is bonus rather than a gap. Nothing an agent needs to call this correctly 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 description coverage is 0%, so the description carries the full burden and does so: it documents search scope (name/description/publisher name), language as a code prefix with examples, the ordering enum with default (-downloads, -created, name), and the limit range 1-100 with default 20. This is meaning well beyond the bare types in the schema.

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 ('Browse published Bible verse collections') plus the three affordances (search, filter, sort). It also distinguishes itself from the sibling get_collection_detail by naming it as the path for unlisted collections, so an agent can route without opening either 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?

Gives explicit when-to-use triggers (finding verses to memorize on a theme like hope/anxiety/forgiveness, or a ready-made memory list for a church group) and an explicit exclusion with the alternative named: collections with `listed` false are not returned, but get_collection_detail 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.