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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral value beyond them: the copy is created as a draft (not published) and carries content, accounts, and per-account overrides, which tells the agent what state the new record lands in.

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?

Two short sentences, zero filler, with the core action front-loaded and the copy behavior following as supporting detail. Every clause 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?

With an output schema present, return values need not be explained, and for a one-parameter tool the description covers action, mechanism, and resulting state adequately. Minor omissions remain, such as what happens if the source post does not exist or lacks accessible accounts, but nothing essential for correct invocation is missing.

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?

There is only one parameter and schema description coverage is 100% ('Post ID to duplicate.'), so the schema fully documents it. The description adds nothing about ID format or source-post requirements beyond what the schema states, making the baseline 3 correct.

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 gives a specific verb ('Clone'), a specific resource ('an existing post'), and the resulting artifact ('as a new draft'), which functionally separates it from create_post and create_from_template among the siblings. An agent can tell what produces the new record without opening any 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?

Usage is implied: clone when you want a copy of an existing post rather than authoring one from scratch. However, the description never explicitly names an alternative (create_post, create_from_template) or a condition for choosing among them, so the routing is left to inference.

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