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

The annotations already mark this as destructive, non-read-only, idempotent, and closed-world. The description adds useful behavioral context beyond the annotations by saying the old text is not kept and the user should be asked to confirm. It does not describe authentication requirements or whether the draft remains pending after the edit.

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 three compact sentences and is front-loaded with the core action. Each sentence contributes necessary information: eligibility, parameter shape, and destructive consequence. There is no redundant or filler wording.

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 simple two-parameter destructive mutation with rich annotations, the description covers the essential usage and safety context. It is slightly incomplete because it does not state the post-edit status or return behavior, but no output schema exists and the annotations already establish the safety profile.

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 description coverage is 0%, so the description needs to compensate. It explains the segments array as one string per post in a thread, which is meaningful, but it does not explain postId or clarify ordering, length constraints, or what happens if the number of segments does not match the thread.

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 states a specific verb and resource: it replaces the text of one saved draft. It also narrows scope to drafts that are still pending or failed. It does not explicitly distinguish itself from sibling tools such as save_drafts, approve_drafts, or send_post_now, so it falls short of a 5.

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?

It clearly states the eligible draft states, pending or failed, and warns the agent to confirm with the user first. It does not explicitly say when another sibling tool should be used instead, such as for creating a draft or sending it, so it is not a full 5.

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