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

Annotations already indicate readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is known. The description adds useful behavioral context: it specifies the maximum number of titles (up to 32), the ordering (by popularity), and that filters apply on top of each other. The phrase 'heartbeat check' also implies the tool makes a live catalog query. No contradictions with 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?

The description is three sentences, each with a distinct purpose: the core action, the output shape, and use cases. It is front-loaded with the main verb and resource, and every sentence earns its place without redundancy or fluff. This is a model of concise, structured documentation.

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, idempotent browse tool with three optional parameters and a defined output schema, the description covers the core functionality, return fields, filter behavior, and typical use cases. It also hints at availability checking via the 'heartbeat' use. With annotations covering safety and the output schema handling return structure, nothing essential is missing for an agent to select and invoke the tool correctly.

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?

The input schema already provides descriptions for all three parameters (limit, topic, languages) with 100% coverage. The tool description mentions 'Optionally filter by language or topic' but does not add syntactic details beyond the schema. Since the schema does the heavy lifting, a baseline of 3 is appropriate; the description reinforces optionality but adds no new semantic information.

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?

The description opens with a specific action and resource: 'Browse the most-downloaded Project Gutenberg books, ordered by popularity.' It then enumerates the returned fields (Gutenberg IDs, authors, languages, download counts), making the tool's output clear. This distinguishes it from sibling tools like gutenberg_get_book (single book) and gutenberg_search_books (search by query), as it explicitly positions itself as a popularity-based discovery endpoint.

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 description gives concrete use cases: 'discovery entry point' with an example query ('what are the most popular classics in French?') and a 'heartbeat check that the catalog is reachable.' This provides clear context for when to invoke the tool. It does not explicitly name alternative tools or state when not to use it, but the examples imply that for specific lookups one would use the get/search siblings. This meets the 'clear context, no exclusions' level.

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