publish_post

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

Beyond the annotations, the description discloses that the post is sent to all connected platforms and adds a critical X-specific constraint: links are rejected in posts, thread segments, and first comments. The billing explanation and the platformContent.twitter workaround give useful behavioral context that an agent could not infer from the annotations 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?

The description is front-loaded with the core action and then moves to the important X constraint. It is mostly efficient, though the billing detail is somewhat verbose and the platformContent.twitter instruction is not actionable through the listed schema.

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 simple one-parameter publish tool with rich annotations, the description covers the main purpose and a significant platform-specific restriction. The remaining gap is that it references platformContent.twitter without explaining how an agent should set that content when the tool only accepts an id.

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?

The input schema has only one parameter, id, and its description already covers its meaning at 100% schema coverage. The description does not add further meaning to id, and its reference to platformContent.twitter does not correspond to any input parameter, so it does not improve parameter clarity.

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 states a specific verb and resource: publishing a draft or scheduled post immediately to all connected platforms. This clearly distinguishes the action from create_post or update_post by focusing on immediate publication of an existing 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 gives clear usage context: use this when a draft or scheduled post should go out immediately. It does not explicitly name alternatives such as update_post or preview_post, nor does it state when not to use this tool, so it falls short of full when/when-not guidance.

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