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

Annotations already declare the tool read-only, idempotent, and non-destructive, so the description does not need to restate those. It adds useful behavioral detail by mentioning cursor-based pagination and the return fields `tweets`, `has_next_page`, and `next_cursor`, which goes beyond 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 well-structured and front-loaded with the core purpose. Every sentence earns its place: what it does, when to use it, what it returns, and how it differs from a sibling tool. No fluff or repetition exists.

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 tool with only two parameters, a read-only/idempotent annotation set, and an output schema, the description covers everything needed to invoke it correctly: purpose, input type flexibility, usage context, pagination behavior, and the relevant alternative. No critical gap remains.

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 description coverage is 100%, so the parameters are already well documented. The tool description confirms that `tweetId` can be a reply or original tweetable, but this mostly mirrors the schema's own description and adds little new semantic detail.

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 states a specific verb and resource: 'Reconstruct the conversation around a tweet.' It clarifies that the tool accepts either a reply or an original tweet and returns the 'surrounding thread,' which clearly differentiates it from sibling tools like get_twitter_tweet_replies_v2.

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 to use the tool: 'Use this when a tweet lacks context on its own and you need the parent chain to interpret it correctly.' It also names the exact alternative for a different need, get_twitter_tweet_replies_v2, and distinguishes 'surrounding thread' from 'replies below a post.'

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