kiwix_search

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

No annotations provided, but description indicates read-only search operation (returns results, no side effects). Does not detail limitations or edge cases, but adequately transparent for a simple search tool.

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 covering purpose, output, and next step. Extremely concise with no irrelevant information.

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?

Tool has 3 parameters and no annotations; description lacks details on pagination (start) and book selection. Output schema may cover returns, but incomplete for parameter context. Adequate but with gaps.

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%, and description provides no explanation for the three parameters (query, book, start). Names alone are insufficient; agent cannot infer valid values or usage for 'book' and 'start'.

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?

Description states 'Full-text search across Kiwix ZIM books' with a specific verb and resource, and lists return items (titles, snippets, URLs), distinguishing from siblings by mentioning alternative tool for full content.

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?

Explicitly recommends using kiwix_fetch_article for full content, providing guidance on when to use alternatives. Lacks explicit 'when not to use' but clearly directs to sibling.

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