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

Goes well beyond annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=false): it discloses cost ('Free'), the two-phase preview/commit behavior, that only the referenced proposal is mutated, and that a lost write reply must be reconciled before retrying. These are exactly the traits an agent needs for a destructive, non-idempotent call.

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?

Four tight sentences, front-loaded with the action and scope, then cost, then confirmation semantics, then retry recovery. No filler; every sentence carries distinct information.

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, gated mutation with no output schema, the description covers scope, cost, preview/commit gating, and retry reconciliation. It does not indicate what a successful approval returns, a minor gap given no output schema exists to rely on.

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% and the schema already documents both proposal_id and the confirm preview/commit semantics. The description largely restates the confirm behavior, adding little meaning beyond the structured fields, 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?

States a specific verb (approve), a specific resource (one existing Website Autopilot proposal) and its source (returned by soclo_page_autopilot). The scope clause 'only that stored proposal changes' pins down the blast radius and separates it from broader autopilot operations.

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 explicit conditional guidance: omit/false confirm yields a preview only, and confirm:true must be used only after the owner approves. It additionally covers the recovery path when a write reply is lost. It never names the reject sibling as the alternative, so routing guidance is implied rather than spelled out.

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