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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds value beyond them: 'All or nothing' (atomicity), 'Needs the sync-schema permission' (auth requirement), and the dryRun default-true workflow plus '1 request' cost hint. It could go further on what happens to indexes that were already managed by the target scope, but the added context is substantive.

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?

The prose is dense and front-loaded, leading with the core action before the selection modes, dryRun workflow, and permission requirement. The telegraphic style ('1 request.', 'All or nothing.') is efficient, though the final fragment is slightly clipped rather than fully self-explanatory.

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 4-parameter destructive mutation with an output schema (so return values need no explanation), the description covers purpose, selection, atomicity, permissions, and the dryRun sequence. It is nearly complete; the only residual gap is target-scope index side effects, which the phrase 'with the indexes the scope manages' only partially addresses.

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%, so the schema already documents all four parameters and the baseline would be 3. The description nevertheless adds semantics not in the schema: scope: null is explained as 'release them from schema sync', and fromScope is characterized as 'Move every list this scope manages, instead of lists' — clarifying the mutual exclusivity intent.

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?

The description opens with a specific verb+resource: 'Move lists to another schema sync scope,' and immediately names the sibling operations it is not (plan_schema_sync/apply_schema_sync territory) by covering assignment and release. It also distinguishes the three distinct outcomes (move, assign unmanaged, release via scope: null), which an agent can act on 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?

It states selection modes explicitly ('Choose lists by id or pathName, or every list of fromScope') and gives a concrete when-to-use example ('e.g. to rename a scope'). The dryRun workflow instruction ('show the user the plan, then call again with dryRun: false') is a precise two-step usage directive rather than generic guidance.

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