Search Knihobot books

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds useful behavioral context beyond those: results are grouped into 'sale-ready title groups,' a physical copy is 'highlighted,' and the returned IDs are intended for downstream detail tools. No contradiction with the 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?

Two sentences, no filler, with the primary action front-loaded and the return value summarized compactly. Every phrase adds useful information without redundancy.

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 13 parameters and many optional filter IDs, the description is too high-level to fully orient an agent. It covers the core search purpose and return shape, and the presence of an output schema and annotations helps, but it leaves filter semantics and defaults such as inStockOnly and languageIds to the schema, which itself is sparse on several parameters.

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 only 38%, and the description does not compensate for the many undocumented filter parameters. It does not explain authorIds, categoryIds, conditionIds, bindingIds, publisherIds, yearMin/yearMax, or pagination behavior. The only implicit semantic link is that 'Search' maps to the required query parameter.

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 states a specific action on a specific resource: 'Search the public Knihobot catalog.' It also clearly characterizes the result as 'sale-ready title groups with the highlighted physical copy, price, availability and IDs needed by the detail tools,' which distinguishes it from sibling detail tools like get_book_detail and list_available_copies.

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 implies this is the entry point for searching the catalog and that results feed into detail tools, but it never explicitly states when to prefer this over suggest_books or get_recommendations, nor does it mention exclusions or when not to use it. Usage context is present but only implicit.

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