Get tweet thread context

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

No annotations provided, so the description fully carries the burden. It discloses return structure: 'original tweet, intermediate replies up the chain, the tweet itself, and direct replies; each tweet includes entities.urls'. It also notes pagination irregularity and single-request nature. Comprehensive for a non-annotated tool.

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?

Two sentences, front-loaded with purpose. Every sentence adds unique value without repetition. No filler or redundant phrasing.

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 no output schema, the description fully explains what is returned (including expanded URLs) and pagination mechanics. Covers all aspects needed for correct invocation: purpose, parameters, behavior, and return structure.

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%, so baseline is 3. The description adds minor value by explaining the cursor parameter's usage ('pass next_cursor back as cursor'), but the schema already describes both parameters adequately. No additional semantics beyond what schema provides.

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 verb 'Fetch', the resource 'conversation thread around a tweet', and the specific use case 'to find links in context'. It distinguishes from sibling tools (get_user_mentions, create_tweet, delete_tweet) by focusing on thread context and link extraction.

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 explains pagination behavior: 'Makes exactly one request per call' and 'pages are uneven... so pass next_cursor back as cursor'. It implies when to use (when needing thread context with links) but does not explicitly state when not to use or list alternatives besides sibling names.

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