twitter_user_tweets

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the return structure and includes 'next_token' for pagination, but lacks details on rate limits, idempotency, or effects of parameters. It adds moderate transparency beyond the schema.

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 concise sentences plus a return type example, all front-loaded with the core purpose and prerequisite. Every sentence adds value, no fluff.

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 8 parameters and no output schema, the description is incomplete. It explains the return structure but fails to cover the many filtering and pagination parameters, leaving significant gaps for a complex tool.

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 0%, so the description must compensate, but it only explains the required 'id' parameter indirectly. The other 7 parameters (exclude, end_time, since_id, etc.) are completely undocumented, leaving the agent with no guidance on their usage.

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 the tool retrieves 'An account's recent posts' with specific examples like 'club announcements, insider news', clearly distinguishing it from sibling tools like twitter_user (user info) and twitter_search_recent (search). It also instructs to resolve the user id first, making the purpose unambiguous.

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 says 'Resolve the id with twitter_user_by_username first', providing a clear prerequisite and usage context. It does not mention when not to use or alternatives, but the prerequisite is valuable for correct invocation.

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