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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so safety is covered. The description adds genuine context beyond that: the operation is 'Free', it returns a preview-only response without confirm, and a lost write reply should be reconciled via soclo_page_get before retrying — a real recovery instruction not present in the structured fields.

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 sentences, purpose front-loaded, no filler. The only mild inefficiency is that the confirm/preview semantics duplicate what the schema already states, though at this length it costs little.

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 single-parameter, destructive mutation with no output schema, the definition covers cost, the two-phase confirm workflow, and failure recovery. It could still say what actually goes offline (page only vs. domain) or what the preview returns, but nothing critical to invoking it correctly is missing.

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 description coverage is 100%, so the schema already documents 'confirm' fully, including the preview behavior and the owner-approval condition. The description restates that logic rather than adding new syntax or format detail, so the baseline 3 is appropriate.

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 states a specific verb and resource ('Take the website offline through the app's save API'), making the operation unambiguous. It does not, however, distinguish itself from adjacent siblings such as soclo_page_set_visibility, soclo_page_remove, or soclo_page_publish, which an agent could plausibly confuse with this action.

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 by the name and by the confirm workflow ('pass confirm:true only after the owner approves'), which is really parameter guidance. The description never states when to choose this over soclo_page_set_visibility, soclo_page_remove, or soclo_page_publish, so an agent must infer the routing.

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