bulk_delete_links

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

With no annotations, the description carries the burden well: it discloses idempotency, that this becomes a WRITE OPERATION when dry_run=false, that the link write scope is required, and that results come back per-pair with a summary. It stops short of explaining partial-failure behavior despite the continue_on_error flag.

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?

Three dense sentences, front-loaded with the primary action and the JSON payload format, with the write-scope warning mid-stream. Only the closing return-value sentence is slightly redundant given an output schema exists.

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 an unannotated batch-mutation tool, the description covers the critical pieces: idempotency, the dry_run safety default, scope requirements, and payload shape. The remaining gaps (continue_on_error semantics, trace_id purpose and failure modes) are real but secondary.

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 0% across 4 parameters, so the description must compensate. It defines the pairs_json element shape ({from_type, from_id, to_type, to_id}) and the write/read semantics of dry_run, but trace_id and continue_on_error are left entirely undocumented.

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 ('remove several directed links'), plus a distinguishing trait (idempotent, batched in one call). An agent can separate it from delete_link and bulk_ensure_links without inspecting schemas.

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 batching scope is implied as the reason to use this over the single-link delete_link, and the dry_run default is surfaced, but there is no explicit when-to-use/when-not statement or named alternative. Minimum-viable routing guidance.

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