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

Goes well beyond the destructiveHint/openWorldHint annotations by stating the effect is irreversible and publicly visible on real networks, and adds a hard procedural requirement — explicit user confirmation in the current turn — that the annotations cannot express. It also discloses the rejection behavior for non-DRAFT posts.

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 tight sentences: action first, consequences and confirmation requirement second, lookup alternative last. No filler, and the most decision-relevant fact (irreversibility) is placed early.

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?

Output schema exists, so return values need not be explained, and the description covers safety, preconditions, and the confirmation gate. The one gap is retry/idempotency behavior, which matters for an irreversible action but is left entirely to the schema's idempotency_key field.

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 on the top-level parameter is 0%, but the nested request properties are extensively self-documented (post_id, platforms, idempotency_key binding rules, natural_posting). The description only echoes 'selected platforms'; it adds nothing about retry keys or platform-subset constraints, so the schema does the heavy lifting.

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 ('Immediately publish a DRAFT post to selected platforms') and distinguishes itself from read-side siblings by naming get_posts(status=DRAFT) as the listing tool. An agent can tell exactly what this does without opening the 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 a clear precondition (post must be DRAFT, non-DRAFT is rejected) and routes to the correct sibling for finding drafts. It does not mention how this relates to schedule_post or review_post, which an agent choosing among publishing paths might also consider.

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