twitter_user_tweets_complete

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

The description goes beyond annotations (readOnlyHint, openWorldHint) by disclosing auto-pagination, the Twitter's ~3200-tweet ceiling, and the return format (flat tweet array). It also mentions that higher max values take longer and cost more. Slight room for improvement: no mention of authentication or error behaviors.

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 three concise sentences with no unnecessary words. It front-loads the core purpose and efficiently covers usage guidance, prerequisites, and limitations.

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?

Given the tool's complexity (auto-pagination, ceiling, cost) and no output schema, the description provides key context: ceiling, return type, prerequisite, and sibling differentiation. It could mention the structure of individual tweet objects or handling of errors, but overall it is sufficient for an agent to use correctly.

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?

The description adds value beyond the schema: it clarifies that user_id must be numeric and resolved from a handle, and for max it provides a default (800) and explains performance/cost implications. Schema coverage is 100% but the description enriches understanding.

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 tool retrieves a user's near-complete original-tweet history in a single call with auto-pagination. It distinguishes itself from the lighter sibling twitter_user_tweets by emphasizing it is for the whole back-catalogue rather than page-by-page.

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 explicitly states when to use this tool: 'use when you want the whole back-catalogue at once'. It also mentions when not to use it (vs page-by-page) and provides a prerequisite: 'Requires the numeric user_id (resolve a handle first with twitter_user_info)'.

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