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 behaviors: creates new post id, re-attaches media/quoteTweetId, enforces link rules, and notes limitations. This provides comprehensive insight into side effects and prerequisites beyond basic schema info.

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 dense but efficient, with every sentence conveying a distinct constraint or behavior. It front-loads the core purpose, then lists limitations and rules without redundancy. Appropriate length for a tool with this complexity.

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?

The description covers essential context: method, prerequisites, limitations, exclusions, and special rules. It omits return value details, but since there is no output schema, some ambiguity remains. Still, for tool selection and invocation, it is sufficiently complete.

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 descriptions cover 100% of parameters, so baseline is 3. The description adds context about the link rule and allowLinksInMainPost defaulting to the draft's stored flag, but this is marginal beyond the schema. It does not significantly enhance parameter understanding.

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 action: 'Edit the root post of a published draft' with a specific verb, resource, and scope. It distinguishes itself from siblings like update_draft (pre-publish edits) and delete_published_draft by focusing on published drafts and the root post.

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?

Provides explicit context: requires X Premium, edits limited, only thread root edited, polls/community posts cannot be edited. It implies when to use (for published drafts) but does not explicitly name alternative tools. Exclusions are clear, but no direct 'use X instead' guidance.

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