Publish post now

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

Beyond annotations, it reveals that publishing is queued to all target channels, requires the post:publish role, and that approver-publishing a pending/rejected post implicitly approves it. These side effects and permission outcomes are behavior an agent couldn't infer from readOnlyHint=false/destructiveHint=false alone.

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 sentences, all high-signal: core action, queue behavior, auth/alternative, and when-to-use. The main effect is front-loaded; no 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?

Covers the action, side effect, permissions, failure mode for contributors, and the edge case of pending/rejected posts. It omits details like invalid-state errors or return payload, but with a single parameter and no output schema these are not critical gaps.

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 fully documents postId with a clear description and 100% coverage, so baseline is 3. The description adds contextual color by saying the post is a draft or scheduled post, but adds no extra constraints or format details.

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 opens with a concrete action — 'Publish a draft or scheduled post immediately' — and specifies the resource and timing. It further distinguishes itself by explaining the approval path (contributors must submit for approval) and that publishing as an approver implicitly approves, separating it from approve_post.

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?

It explicitly states the intended trigger: 'Use this when the user wants to publish an existing draft or scheduled post right now.' It also gives when-not: contributors without post:publish get 403 and should use create/update with requestApproval instead.

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