publish_post

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

With no annotations provided, the description carries the burden. It discloses a key behavioral requirement for live publishing (liveConfirmation + summary) and mentions the dry-run alternative. However, it does not disclose side effects, permissions, reversibility, or return format. It adds some transparency but is incomplete for a mutation tool.

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?

The description is compact and front-loaded: two sentences, no filler. It efficiently states the main action and the critical requirement for live publishing.

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?

Given the tool's complexity (7 parameters, nested objects, no output schema, no annotations), the description is too brief. It explains dry-run vs live but omits specifics like what a publish record is, platform auth prerequisites, scheduling behavior, and error conditions. The description does not adequately prepare an agent 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 description coverage is 0%, and the description only explains liveConfirmation (its confirmed and summary fields). It does not clarify title, body, platforms, tags, media, or scheduledAt. With seven parameters and no parameter documentation in the description, it fails to compensate for the schema gap beyond one parameter.

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 clearly states the tool's purpose: 'Publish a post or create a dry-run publish record.' It uses a specific verb and resource, and the dry-run nuance adds clarity. It does not explicitly distinguish from sibling tools like prepare_post, but the core action is unambiguous.

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?

The description implies usage by noting that live adapters require liveConfirmation.confirmed=true and a summary, suggesting that either live publishing or dry-run is possible. However, it does not explicitly state when to use this tool versus prepare_post or check_publish_status, nor does it mention exclusions. The guidance is implied rather than explicit.

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