kiwix_list_books

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

The description accurately indicates a read-only listing operation. With no annotations provided, the description carries the burden; it is straightforward and sufficient for this simple case, though lacking explicit safety notes.

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, no filler. Front-loaded with the main action. Every word adds value.

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?

Given no annotations and low schema coverage, the description covers the essential purpose and filtering. The presence of an output schema reduces the need to describe return values. Minor improvement could mention scope of listing (e.g., all local books).

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 single parameter 'query' is described as an optional filter by title keyword, adding meaning beyond the schema's type and default. No further details (e.g., case sensitivity) given, but it's adequate for a simple filter.

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 clearly states it lists ZIM books from a Kiwix server, with a specific verb and resource. It distinguishes from sibling tools (fetch_article, search) by focusing on listing books.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies usage via 'list' and 'optionally filter', but lacks when-not or context for choosing between siblings.

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