Publish post

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

With no annotations provided, the description carries the full burden. It discloses the confirm requirement, independent platform failure with setup instructions, and the special behavior of 'export' always succeeding. This goes beyond a simple 'publish' statement, though it omits side effects or success return details.

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 three sentences, with the purpose front-loaded, followed by the critical safety condition, then platform behavior. Every sentence adds value; no redundancy or 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?

For a tool with no output schema, the description covers the essential operational aspects: confirmation, per-platform failure modes, and the export special case. It does not describe return values or async behavior, but the critical user-approval and partial-failure semantics are well covered.

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 67% (confirm and platforms have descriptions, draftId does not). The description adds depth for confirm (explicit user approval) and clarifies platform failure behavior, but it does not explain draftId or the subset-filtering aspect of platforms beyond what the schema already states.

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 starts with 'Publish a draft to its target platforms,' which clearly states the action (publish), the resource (draft), and the destination (platforms). This distinguishes it from sibling draft-creation tools like create_post_draft and create_thread_draft.

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 explicitly states the key usage condition: 'Requires confirm: true — never call this without the user’s explicit go-ahead in the conversation.' This provides clear when-to-use guidance. It does not mention alternatives, but the context of publishing vs. creating drafts is evident from the sibling tools.

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