create_post_variants

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

Annotations cover the safety profile (non-read-only, non-destructive, non-open-world), and the description adds real behavioral context: variants surface as tabs the user compares/edits/comments on, and only the main post is scheduled. It does not state whether adding variants overwrites or merges with existing ones (relevant given delete_variants/promote_variant siblings), so it stops short of a 5.

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?

Four dense sentences, front-loaded with what the tool does, followed by sequencing, editing, and the sibling alternative. No 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 3-parameter mutation tool with no output schema, the description covers purpose, ordering, UI behavior, and alternatives, which is nearly complete. It leaves the return/confirmation behavior and the merge-vs-replace semantics of existing variants unstated, a minor gap.

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 the baseline is 3, but the description adds meaning beyond the schema: it introduces the variant slug identity used later with set_post variant=<slug>, and illustrates the 'name' field with real examples ('Story first', 'Shorter', 'Single tweet').

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 (add) and resource (other versions of the session's LinkedIn or X post) with concrete examples of variant types. It is clearly distinguishable from set_post (main post), set_post_hooks (different openings), and promote_variant/use_post_variant (selection).

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?

Explicit sequencing is given ('Write the main post with set_post first'), along with how to edit later ('set_post variant=<slug>') and the disambiguating alternative for a different use case ('For different openings of the same post use set_post_hooks'). The agent knows when and when not to call this.

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