aiworkhub_manager_semantic_edit_apply

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

With no annotations, the description does real work by warning that `new` replaces the WHOLE prepared range and that every kept line must be re-emitted — the single most important failure mode for this tool. It does not disclose what happens on a stale/mismatched hash, nor how idempotency_key affects retries.

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 short lines, front-loaded with the destructive-scope warning before the parameter notes. Terse but every sentence carries information; 'hash-bound' and 'escape level' remain unexplained jargon.

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 mutation tool with zero annotations, an output schema present, and 3 required params, the description covers the main hazard but omits the prepare prerequisite, hash-mismatch behavior, and idempotency semantics — all things an agent needs before invoking it 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 coverage is 0%, so the description must compensate: it explains `new` (full-range replacement semantics) and `allow_escape_level_change` (only for intentional regex/escape fixes). `target_id` and, more importantly, `idempotency_key` receive no explanation at all, leaving half the required inputs opaque.

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 (replace) and resource (exactly one prepared, hash-bound range), with a scope quantifier that pins down the blast radius. It does not name the sibling aiworkhub_manager_semantic_edit_prepare explicitly, so the pairing is only inferable from the word 'prepared'.

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 rather than stated: 'prepared, hash-bound range' suggests this only applies to a range created by the prepare sibling, and the escape-level line gives a conditional for one parameter. There is no explicit when-to-use/when-not statement and no named alternative.

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