socials_create_post

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

With no annotations, the description carries full burden. It discloses the UI automation steps (opens compose dialog, fills text, attaches media, clicks Post) and the environment prerequisite (agent tab on X with left nav visible). It also highlights the need to confirm with the user. While it doesn't discuss reversibility or failure modes, the key behaviors are transparent.

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, with two sentences capturing the core action and prerequisites, plus a prominent IMPORTANT note for user confirmation. No filler or redundancy.

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 UI automation nature, the description covers prerequisites, actions, and a safety check (confirmation). The schema fully describes parameters. It doesn't mention post-publish result, but with no output schema and a straightforward create operation, the essential context is present.

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 baseline is 3. The description mentions optional media attachment and filling text, but these are already covered by the schema's parameter descriptions. It adds no new parameter-level detail beyond what the schema provides.

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 it publishes a new original post on X (not a reply), distinguishing it from reply and quote tweet siblings. It also specifies the pinned agent tab context, making the tool's purpose 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 clarifies when to use it by excluding replies and noting it's for original posts, implicitly differentiating from socials_quick_reply and socials_x_quote_tweet. It also provides situational prerequisites (pinned tab on X, left nav visible) and a mandatory user confirmation step. However, it does not explicitly name alternative tools for other scenarios.

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