Recover book metadata

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

Adds significant detail beyond annotations: explains it does an online lookup using ISBN or text, uses specific sources, and returns a changes object without writing. Aligns with readOnlyHint and openWorldHint. 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?

Two concise sentences. First sentence states action and sources, second emphasizes preview-only nature. No redundant information.

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?

Covers key aspects: purpose, side-effect-free, sources, output shape (changes object). Lacks error handling or fallback behavior details, but output schema is provided separately, so overall complete enough for effective use.

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 0%. Description implies id/bookId identify the book and library specifies the library, but does not explicitly describe each parameter. Sources are mentioned in the lookup context. Some inference needed, but adequate for basic use.

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?

Describes a specific action: proposing real metadata for books with missing/raw-filename titles via online lookup on Open Library and Google Books, returning a changes object. Clearly distinguishes from siblings like calibre_get_book and calibre_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?

States when to use (missing/raw-filename title) and that it is preview-only (never writes). Implicitly guides to use calibre_update_book afterward. Could be more explicit about when not to use or alternatives, but sufficient.

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