bulk_set_metadata

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

With no annotations, the description carries the full burden. It mentions that 'fields' works like set_metadata (replaces the field), but does not disclose whether the operation is reversible, what happens if query matches no books, or if there are any limits or side effects.

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 sentences plus a caution; every sentence serves a purpose. The main action is front-loaded, and the caution is placed at the end. No wasted 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 no output schema, the description does not need to explain returns. It covers purpose, usage, and param semantics well. However, behavioral transparency is slightly lacking, preventing a 5.

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 adds value by explaining that 'query uses Calibre syntax' (already in schema) and that 'fields works like set_metadata (replaces the field)'—the latter is not present in the schema description and clarifies behavior.

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 'Applies the same metadata to ALL books matching a search', specifying the verb, resource, and scope. It distinguishes itself from the sibling 'set_metadata' which works on individual books.

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?

Explicitly provides a use case (organizing in bulk) and an example (setting series or publisher). It also warns against using for adding tags without removal, directing to 'add_tags per book' as an alternative.

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