publish_post_now

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

Annotations already declare write, non-idempotent, open-world, non-destructive, but the description discloses the genuinely non-obvious behavior that delivery is asynchronous via the scheduler and not synchronous, plus how to verify it went live. This is high-value context beyond the annotations, though it says nothing about rate limits or failure/retry behavior.

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?

Three sentences, front-loaded with the action and its timing caveat, with no filler. Slightly clunky phrasing in the middle sentence ('it is not published synchronously') and the trailing field-parity note are minor deductions.

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 20-parameter, nested-object, no-output-schema tool, the description covers the critical operational risk (async delivery) and routes the agent to list_scheduled_posts/verifiedLive to confirm success, which substitutes for a return-value contract. The heavy platform-specific parameter space is fully handled by the schema.

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 100%, so all 20 parameters including the nested platform-specific 'options' object are already documented. 'Same fields as schedule_post' adds a useful parity signal but no parameter-level meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Publish to one connected account right away') and immediately scopes it against the sibling operation by contrasting with 'instead of scheduling'. An agent can distinguish this from schedule_post without opening either schema.

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?

Explicitly frames this as the alternative to scheduling and gives a concrete follow-up procedure ('call list_scheduled_posts afterwards and check verifiedLive'). It does not spell out when NOT to use it (e.g. for drafts or reviewing before publish), which keeps it short of a 5.

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