twitter_tweet_thread

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

Annotations already establish read-only safety (readOnlyHint: true, destructiveHint: false). The description adds value by explaining the tool returns the full ordered sequence in a single call and specifically excludes replies, providing context on the output shape without contradicting the annotations.

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 two sentences, front-loaded with the core purpose, includes a critical exclusion, and contains zero redundant words. It efficiently conveys all essential information without excess.

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 read tool with no output schema, the description fully covers what it does, how to invoke it (any id/url), and what it excludes, making it sufficient for an agent to correctly select and use it. No significant behavioral details are missing.

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 coverage is 100% with clear descriptions for id and url, and the schema already notes 'Provide exactly one of id or url'. The description adds the crucial detail that any tweet id or URL from the thread works, reinforcing flexibility beyond the schema's basic field descriptions.

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 uses a specific verb+resource ('Get all tweets in a thread') and clearly defines the scope (same author, ordered sequence). It distinguishes itself from the sibling tool twitter_tweet_replies by explicitly limiting to the author's own tweets, avoiding confusion.

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 explicitly states when NOT to use it ('Does NOT return replies from other users') and directs to the alternative twitter_tweet_replies. It also gives practical usage guidance ('Pass any tweet id/url from the thread'), but does not exhaustively cover all possible exclusions or alternative tools, so not a perfect 5.

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