publish_post_now

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action and immediacy but does not mention potential side effects like whether the post loses its scheduled status, if the action is reversible, any permission requirements, or rate limits. This is a notable gap 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 a single, compact sentence that immediately conveys the action, target, and timing. No filler words; every word earns its place.

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?

The description is clear at a high level but omits details such as what happens to the original scheduled post, how 'platforms' are determined (e.g., connected accounts), and any prerequisites. Given the absence of annotations and an output schema, these gaps leave the description only modestly complete.

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 schema provides 100% coverage for the single parameter 'id' with a clear description. The tool description adds the useful constraint that the post must be an 'existing scheduled post', which is meaningful context beyond the schema's generic 'post to publish' description.

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 uses the specific verb 'broadcast' and clearly identifies the resource as an 'existing scheduled post' with the immediate action of publishing to platforms. This distinguishes it from sibling tools like create_post, update_post, and delete_post, which handle different operations.

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 clearly implies the use case: publishing a previously scheduled post right away. However, it does not explicitly mention alternatives or state when not to use it, though the sibling list provides no other tool for this action, making the context clear.

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