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

Adds rich context beyond annotations: the preview gating via confirm, immediate visibility on live site, the no-credit cost, and the reconciliation procedure for lost writes. Annotations declare destructiveHint=true and idempotentHint=false but the description explains the practical implications.

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?

Dense but every sentence carries operational weight: preview gating, cost, live visibility, reconciliation. Could be split into bullet-like clauses but remains readable.

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?

Covers preconditions (if_unchanged), safety (confirm gating), cost, and failure recovery (reconciliation). No output schema exists, so the description would ideally hint at the preview return, but the preview-only behavior is implied.

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 baseline is 3, but the description adds value by tying if_unchanged to the displayed revision from soclo_page_pages and explaining the confirm flow. Reinforces rather than just repeats schema text.

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 (Save/Reorder) and resource (page ids in navigation order). Distinguishes from siblings like soclo_page_rename and soclo_page_save by specifying navigation-order semantics.

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?

Gives clear conditions: pass confirm:true only after owner approval, without it returns preview. Also flags which related tools to read from (soclo_page_pages, soclo_page_versions) for reconciliation. Doesn't explicitly compare against soclo_page_save though.

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