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

Annotations already declare non-read-only, non-destructive, idempotent, but the description adds real context an agent needs: nothing is deleted, it alters what publishes to the user's live social accounts, user confirmation is mandatory, the default keeps the post's day while keepDay:false drops it to Unscheduled, and already-published/publishing posts are rejected. Per-item result semantics for batch calls are also disclosed.

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?

One dense paragraph, front-loaded with the core action and safety warning before the option details; nearly every clause carries information. It is on the long side and could be split into short lines for scanability, but nothing is redundant filler.

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?

No output schema exists, and the description covers what an agent needs for a live-account mutation: confirmation requirement, the default placement, batch semantics with per-post answers, and refusal cases. Nothing material is missing for correct invocation.

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 baseline is 3; the description earns slightly above that by framing the postId-vs-postIds choice with a real use case ('a week being replanned') and by tying keepDay to the downstream re-scheduling workflow. It largely restates the schema's own semantics rather than adding format or constraint detail.

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 and resource ('Takes scheduled posts back to drafts so they no longer go out') and explicitly anchors it to a familiar UI action ('the same as the Unschedule button on the Plan page'). It is clearly distinguishable from delete_post (nothing is deleted), schedule_post, and approve_week, which are named as the re-scheduling path.

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-to-use ('a week being replanned'), when-not-to-use (a post that already went out or is publishing right now is refused), the prerequisite ('ask the user first, then pass confirm: true'), and the follow-up alternatives (schedule_post or approve_week). No inference is required to pick this tool.

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