bookshelf_import_lists

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly labels WRITE and DESTRUCTIVE operations, which is valuable. However, it does not disclose other behaviors like rate limits, idempotency, or failure modes, so credit is given for the safety notes but not for full transparency.

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 lengthy due to 16 operation listings, but it is well-structured as a bulleted list with the core instruction front-loaded. Every line conveys specific operation details without redundancy. The formatting is efficient and scannable, though it could arguably be trimmed by grouping similar operations.

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 tool's complexity as a dispatcher, the description covers the operation/arguments pattern, enumerates all supported operations with signatures, and notes safety for write/delete operations. With an output schema present, explaining return values is unnecessary. The description is thorough enough for an agent to understand how to invoke it correctly.

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 schema has 0% description coverage, so the description must compensate. It lists each operation's signature, including parameter names and defaults (e.g., force_save=False, body={}), which provides some semantics. However, it does not explain the structure or expected keys within the `arguments` dict beyond 'matching that operation's parameters'. This is partial but not comprehensive.

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 identifies this as a dispatcher for Bookshelf import list operations, listing all sub-operations. It distinguishes itself from sibling tools by domain scope (import lists vs. media library, profiles, etc.). The verb is implicit but understandable; it's not a tautology, though it could be more specific about what 'import lists' represent.

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 explains the general usage pattern (pass an `operation` and an `arguments` dict), but it does not explicitly state when to use this tool over alternatives. Since siblings cover other Bookshelf domains, the intended context is implied but not stated. No exclusions or prerequisites are mentioned, so it's adequate but not fully explicit.

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