Search Rakuten Books (DVDs / Blu-ray)

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds the specific return fields (performer, label, JAN, list price, review stats), complementing the annotations. No contradictions.

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 concise, with two sentences in English followed by a Japanese translation. It front-loads the purpose and key details without unnecessary words.

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 the 9 optional parameters and no output schema, the description adequately summarizes the return fields. However, it could mention pagination support or sort options, which are covered in the schema.

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 100%, so the baseline is 3. The description paraphrases some parameter options (title, performer, label, JAN) but does not add meaning beyond the schema descriptions, which are already clear and bilingual.

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 Rakuten Books for DVDs and Blu-ray discs, differentiating from sibling tools like books_book_search or books_cd_search by specifying the media type. It provides the search fields and return details.

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 usage for DVD/Blu-ray searches but offers no explicit guidance on when to use this tool over alternatives or when not to use it. Sibling tool names provide context but the description itself lacks comparative guidance.

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