create_thread

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Post' implies a write/mutation operation, the description doesn't disclose authentication requirements, rate limits, whether the thread is published immediately, error conditions, or what happens if media attachments fail. This is inadequate for a mutation tool with zero annotation coverage.

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 a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for the tool's apparent complexity and front-loads the core functionality.

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 mutation tool with 2 parameters and no annotations, the description is insufficiently complete. While an output schema exists (which reduces the need to describe return values), the description doesn't address authentication needs, error conditions, or parameter semantics. It provides basic purpose but lacks operational context needed for safe invocation.

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?

With 0% schema description coverage for both parameters, the description provides no information about parameter meanings, formats, or constraints. It doesn't explain what 'tweets' array should contain, what 'media_paths_per_tweet' represents, or how these parameters interact. The description fails to compensate for the complete lack of schema documentation.

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 ('Post') and resource ('a thread of multiple tweets'), making the purpose immediately understandable. It distinguishes from sibling 'post_tweet' by specifying multiple tweets in a thread. However, it doesn't fully differentiate from 'quote_tweet' which also involves multiple tweets.

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?

The description provides no guidance on when to use this tool versus alternatives like 'post_tweet' for single tweets or 'quote_tweet' for quoting existing tweets. There's no mention of prerequisites, constraints, or typical use cases for thread creation versus other posting methods.

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