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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is partly covered. The description still adds real context the annotations cannot: the platform-level no-unpublish constraint, the refusal behavior instead of a failed attempt, the dry-run preview when confirm is absent, and the publish:post permission requirement. That is substantive but slightly repetitive of the confirm schema text.

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 sentences, front-loaded with the core action and scope. All sentences earn their place, though the parenthetical '(and Soclo generally)' is slightly loose and the platform list could be trimmed.

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 two-parameter mutation with no output schema, the description covers everything an agent needs: what can be cancelled, what cannot and why, the confirm-gating semantics, and the required scope. No return-format gap matters since the confirm flag defines the two response modes.

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 explains that confirm=true means owner approval and that omitting it produces a preview. The description largely restates this, so baseline 3 applies — no additional syntax, format, or ID-provenance detail beyond what the schema carries.

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?

Names a specific verb and resource plus a hard scope qualifier: 'Cancel ONE post that is still scheduled.' An agent can distinguish it from soclo_posts_reschedule, soclo_posts_edit_draft, or soclo_page_unpublish without opening any 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?

Gives explicit when (post is still scheduled), explicit when-not (post already publishing or live — the tool refuses rather than attempting), and the gating condition for the confirm flag. The only omission is naming a sibling as an alternative, which is moot here since no other tool can unpublish.

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