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

Annotations already declare a non-destructive write (readOnlyHint=false, destructiveHint=false), so the safety profile is covered. The description usefully adds that the output is a draft rather than a published or scheduled post, but says nothing about what the copy inherits (caption, media, tags) or whether the original is touched — relevant behavioral context for a duplication 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?

A single front-loaded sentence with the action, the resulting artifact, and the intended follow-up; nothing redundant and nothing padded.

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 no output schema, the description carries the burden of describing the result, and 'draft copy' is only partially sufficient — it is unclear whether the duplicated draft keeps the original's schedule, media, or captions. Adequate to invoke the tool, but the post-condition is underspecified.

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 50%: idempotencyKey is documented thoroughly in the schema, while postId has no description. The description implies postId is the source post being copied, which is the bare minimum, but adds no format or constraint detail. Baseline 3 fits given the schema does most of the work for the one non-obvious parameter.

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 ('create a draft copy') and resource ('an existing post'), and the word 'copy' plus 'draft' separates it from create_post (a fresh post) and recycle_post. It does not name any sibling explicitly, so the differentiation is implicit rather than stated.

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?

'Ready to edit and reschedule' implies the scenario where this tool fits, but there is no explicit when-to-use/when-not guidance and no pointer to recycle_post or duplicate_automation, which an agent would need to choose correctly among similar tools.

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