draft_thread

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

With no annotations provided, the description carries the transparency burden and does it well: it states it does not post, returns drafts for review, and requires a SHIPPOST_API_KEY. It could add minor details like rate limits or cost, but the key side effects and prerequisite are disclosed.

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 compact and front-loaded: first statement defines the action, second states safety/deliverable, third covers prerequisites. Every sentence earns a purpose with no filler.

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?

Given the output schema is present and all three parameters are reliably documented, the description has enough context. It covers what the tool does, that it doesn't post, and the required API key setup, making it complete for a drafting 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?

The schema already provides 100% coverage with meaningful descriptions for topic, style, and length. The description adds little beyond the schema, so it doesn't meaningfully deepen parameter understanding, though no gaps exist.

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?

Starts with a specific action and resource: 'Draft a tweet thread about a topic in your voice using AI.' It also clarifies the deliverable ('Returns DRAFTS — does not post'), which distinguishes it from posting tools like post_tweet and single-tweet sibling draft_tweet.

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?

Gives clear workflow guidance: use it to create drafts, not to publish, and explicitly directs the agent to 'use post_tweet() for each' after review. It doesn't explicitly contrast with draft_tweet or draft_reply, but the thread framing and post_tweet pointer make usage context reasonably clear.

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