Get Knihobot recommendations

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds 'recommended by Knihobot' but does not disclose additional behavioral details such as result stability, pagination, or recommendation criteria. No contradiction 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?

A single declarative sentence that front-loads the action ('Return books') and the resource ('recommended by Knihobot') with no filler or redundant wording.

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 simple read-only lookup with a required editionId, detailed output schema, and strong annotations, the essential call context is present. The only notable gap is the lack of clarification on how recommendations differ from suggest_books, which is a minor omission.

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 description reinforces that editionId is the target edition, which the schema already documents as 'Knihobot mother/edition ID'. It adds little for limit, though limit's default, minimum, and maximum are already in the schema. 50% schema description coverage is only partially compensated by the description.

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 clear action and resource: return books recommended by Knihobot for a specific edition. It is distinct from search_books, get_book_detail, and list_available_copies, but it does not explicitly differentiate itself from the similarly named suggest_books sibling.

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?

Usage is implied: call this tool when you have a specific editionId and want Knihobot's recommendations for it. However, there is no explicit when-not-to-use guidance or mention of alternatives such as suggest_books, leaving the selection decision partially to inference.

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