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

Annotations declare write (readOnlyHint=false), non-destructive, and closed-world, so the description is not contradictory. However, it adds no behavioral context - it doesn't say whether the existing post content is replaced (destructiveHint=false suggests it isn't, yet rewriting sounds like replacement), whether it consumes AI credits, or whether the operation is long-running.

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?

It is a single short sentence, but that brevity comes from omission rather than economy - the sentence adds no information beyond the tool name, so it does not earn its place as documentation.

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 three required parameters, no output schema, and terse annotations, the description carries the full burden and delivers essentially nothing about input sourcing, behavior, or results. It is inadequate for invoking this tool correctly.

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?

All three required identifiers (projectId, siteId, postId) have 0% schema description coverage, and the description mentions none of them. An agent gets no signal about what these IDs refer to or where to obtain them, so the description fails to compensate for the schema gap.

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?

"Write a post again with AI" essentially restates the name and title (regenerate = write again, distribution post = post) without naming the resource domain or distinguishing it from siblings like edit_distribution_post or regenerate_article_fields. It conveys only that AI is involved.

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?

No when-to-use guidance whatsoever: it does not say whether this should be preferred over edit_distribution_post, whether it requires an existing post to already exist, or what state the post must be in. The tool name implies a regeneration of an existing post, but the description states nothing.

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