watchlist_import

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

Annotations declare destructiveHint=false, but the description says replace performs clear-and-append, i.e. clearing existing entries before writing. That is a direct contradiction of the destructive hint, even though the description also adds useful safety context such as idempotency and post-write order verification.

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 compact sentences with no wasted language. The core scope and the merge/replace distinction are front-loaded.

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?

For a 9-parameter mutation tool with no output schema, the description covers the central behavioral distinction and replace safety conditions. Remaining parameter details such as target_id, expected_layout_id, and dry_run are handled by the schema, though broader tool-choice guidance is still missing.

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 67%, and the description adds conditional semantics not present in the schema: replace requires an idempotency key and verifies the full requested order after clear-and-append. Several parameters are left to the schema, but the key mode/idempotency semantics are materially clarified.

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?

States a specific verb/resource: import explicit entries, and distinguishes merge versus replace behavior. It never explicitly names the watchlist target or the sibling watchlist_import_preview, so sibling differentiation is incomplete.

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?

Explains mode behavior enough to imply when merge or replace is appropriate, and notes the idempotency-key condition for replace. It gives no explicit when/when-not guidance versus watchlist_add_bulk, watchlist_set_entries, watchlist_import_preview, or watchlist_reconcile.

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