Edit published draft on X

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

With no annotations, the description fully discloses key behaviors: new post IDs are created and stored locally, media and quoteTweetId are re-attached, and editing is limited. This exceeds typical descriptions and gives the agent a solid understanding of side effects.

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 sentences, front-loaded with the core action, and each sentence provides meaningful operational detail without redundancy.

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?

Despite lacking an output schema, the description covers essential operational aspects: permissions, limitations, side effects, and scope. There is no obvious missing information for an agent to select and invoke the tool.

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 parameters are documented in the schema with clear descriptions. The tool description adds no additional parameter-specific meaning beyond what the schema provides (e.g., it mentions media re-attachment but this is not parameter-related). Therefore, baseline 3 is appropriate.

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 clearly states the tool edits the root post of a published draft, specifies the endpoint and edit mechanism, and notes that only the root is edited, which distinguishes it from other draft-related tools like update_draft and publish_draft.

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 provides clear conditions for use: requires X Premium, time/edit limits, and excludes polls and community posts. It also clarifies scope (thread root only). However, it does not explicitly name alternative tools for other scenarios, so it misses the 'alternatives' criterion for a 5.

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