Search Rakuten Books (Printed Books)

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. The description adds valuable behavioral details: returns book details including ISBN, author, publisher, series, table of contents, preview URL, list price, and review stats. No contradictions 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?

The description is two concise English sentences (plus Japanese translation) with zero wasted words. It front-loads the purpose and key details.

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 high schema coverage and clear annotations, the description is complete: it lists return fields, requires at least one search parameter, and defines scope. No output schema exists, so the description adequately covers return value expectations.

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 100%, but the description adds the constraint that at least one search field must be provided, which is not in the schema. It also summarizes the search fields, though the schema already describes each 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 clearly states it searches for printed books by title, author, ISBN, publisher, or keyword, distinguishing it from sibling tools for CDs, DVDs, ebooks, etc. It specifies 'printed books' explicitly, differentiating from kobo_ebook_search.

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 includes the critical guideline to 'Pass at least one search field.' It implies when to use via context (printed books vs. other media), but lacks explicit exclusions or alternative tool mentions.

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