add_watch_target

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, and the description adds the meaningful detail that the local bridge requires confirm_action=true after user approval. It remains silent on duplicate handling, the 100-item batch cap, idempotency replay semantics, and whether partial failures roll back — all relevant for a mutation with four required parameters.

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 short sentences, front-loaded with the core action and followed by the gating caveat. No filler, no restatement of the tool name.

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 four-required-parameter mutation with no output schema and sparse schema descriptions, the description is too thin: half the parameters are effectively undocumented anywhere, and the description never states what the tool returns or how batch adds behave. Only the confirm_action flow is adequately conveyed.

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 only 25% (only confirm_action is documented in-schema), so the description is expected to compensate. It explains confirm_action and hints that watchlist_id must be an owned watchlist, but says nothing about usdots being a 1-100 array of USDOT numeric strings or about what idempotency_key guarantees on retry.

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 and resource: 'Add a carrier to an owned watchlist.' The word 'carrier' implicitly distinguishes it from the sibling add_authority_watch_target, though it never names that sibling explicitly. An agent can identify what the tool does without opening the schema.

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?

'Owned watchlist' encodes a prerequisite, and the confirm_action sentence describes a gating step, which is useful usage context. However, there is no explicit guidance on when to use this versus add_authority_watch_target, and no guidance on how to obtain a watchlist_id or what to do when the same USDOT is already present.

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