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

Annotations already flag this as a destructive, non-read-only mutation, and the description adds real value beyond them: it says the collection and field mapping are both cleared, that the change lands on the page's draft under the revision lock, and that it is validated against the section's current anchor. It does not say what happens when the section is already unbound (no-op vs error) or whether a publish is then required.

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 user-visible effect, then the inverse operation, then implementation behavior. Slightly jargon-heavy ('SET_COLLECTION operation', 'revision lock', 'current anchor') but nothing is padded.

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 destructive mutation with no output schema, the description covers what changes, what is destroyed, and the draft/lock/anchor mechanics an agent needs. The remaining gap is outcome on already-unbound sections and the publish implication, which an agent would still have to discover.

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 100% and every parameter is described in the schema, including idempotencyKey retry semantics, so the baseline is 3. The description only loosely reinforces identifiers via mentions of 'the section's current anchor' and 'the page's draft' without adding format or constraint detail.

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 ('Disconnect a Uislice section's collection binding') and its effect ('no longer renders entries from a collection'). It explicitly names and contrasts with the sibling bind_section_to_collection, so an agent can route between the pair without opening either 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?

The sentence 'Reverses bind_section_to_collection' gives a clear usage context and names the inverse operation. It doesn't cover adjacent alternatives such as remove_section or what to do if the section has no binding, so it stops short of full when/when-not guidance.

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