Search books

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

Annotations already declare readOnly, idempotent, and open-world hints, so the bar for extra disclosure is lower. The description adds useful behavioral facts beyond annotations: results are capped at 100 hits and search cards omit pricing. This helps the agent set expectations without contradicting 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?

Four tight sentences front-load the main purpose, then add return-value context, a sibling-tool pointer, and a key limitation. Every sentence contributes information with no filler or repetition.

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?

With no output schema, the description covers the main return elements (works with author line, matched edition ids) and the important caveats (no price, 100-hit cap). It stops short of describing the full card structure or pagination behavior, but the essential information for invoking correctly is present.

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 coverage is 67%, and the description adds meaning by explaining what query can contain (title, author, keyword, Persian or English), reinforcing the schema's examples. The sort enum is self-explanatory, and the description does not need to restate it. There is minor room for more detail on how sort interacts with the 100-hit cap, but the core semantics are clear.

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 ('Search iranketab.ir for books'), the resource, and the search dimensions (title, author, keyword in Persian or English). It also distinguishes itself from book_details by explicitly noting that search cards carry no price.

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 clear context: use this for broad search by title/author/keyword, and explicitly routes price/translator/stock needs to book_details. It does not enumerate when to use sibling search tools like similar_books or find_author_publisher_or_tag, so some alternative guidance is left implicit.

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