watchlist_add_bulk

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

Annotations already declare it as a non-destructive, idempotent write operation with open-world access. The description adds useful behavioral context: it only appends missing entries and verifies the complete watchlist afterward, which is valuable beyond the annotations. It doesn't cover authentication or rate limits, but that's less critical here.

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 a single, dense sentence with no wasted words. It is front-loaded with the primary action and then the verification step, making it highly efficient.

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 annotations (idempotent, non-destructive write) and schema (with descriptions for most parameters), the description covers the key behavior (append missing entries) and the verification step. It could be slightly more complete by mentioning constraints like maximum entries or handling of sections, but it is adequate for an agent to use the tool 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?

Schema description coverage is high (67% or more, with most parameters documented). The description does not add meaning beyond the schema; it only hints at the 'entries' parameter's content ('exact symbols/sections') and the 'missing' condition, which is already implied by the schema's descriptions.

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 states a specific verb ('Append') and resource ('missing exact symbols/sections') for a watchlist, making the purpose clear. It does not explicitly differentiate from siblings like watchlist_add or watchlist_set_entries, but the bulk nature is implied by the name and description.

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?

Usage is implied: it should be used to append missing entries in order, and it independently verifies the result. However, there are no explicit guidelines on when to use this versus alternatives such as watchlist_add or watchlist_set_entries, nor any exclusions.

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