get_user_tweets_complete

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

Annotations already declare readOnlyHint=true, so the description correctly implies a read operation. It adds the behavioral detail 'self-thread expansion', but does not explain what that entails (e.g., whether it expands tweets into full threads), nor does it mention other behaviors like rate limits, pagination beyond the cursor, or content inclusion (e.g., retweets).

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 sentence that is concise, front-loaded with the main action, and contains no filler. Every word adds value.

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 read-only tool with well-described parameters, the description is adequate but lacks details on the 'self-thread expansion' behavior and potential limitations. Given the complexity of thread expansion and the number of similar sibling tools, some additional context would improve completeness.

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 both parameters well-described in the schema. The description adds no additional meaning beyond what the schema provides (cursor as pagination token, userName as screen name). With high coverage, baseline of 3 is appropriate.

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 'Fetch tweets and replies posted by a Twitter user with self-thread expansion', which specifies the verb (Fetch), resource (tweets and replies), and a unique distinguishing feature (self-thread expansion) that separates it from sibling tools like get_user_tweets, get_user_tweets_and_replies.

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 explicit guidance on when to use this tool versus alternatives. It does not contrast with sibling tools such as get_user_tweets (which lacks replies) or get_user_tweets_and_replies (which may not include self-thread expansion). No when-not-to-use or prerequisite information is given.

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