twitter_user_tweets_and_replies

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

Annotations already indicate readOnlyHint=true, openWorldHint=true, destructiveHint=false. The description adds context about the timeline content but does not disclose rate limits, authentication needs, or data freshness. The description is consistent with annotations, not contradicting.

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 concise with two sentences covering purpose, usage guidance, and pagination. No extraneous words; every sentence 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?

Given the complexity of a full timeline tool with many siblings and no output schema, the description provides adequate context: differentiates from siblings, mentions pagination. However, it does not explain the response format, which would be helpful for a tool that returns a timeline of mixed content types.

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 schema already describes all 4 parameters with 100% coverage. The description does not add significant meaning beyond the schema, only mentioning cursor for pagination. With full schema coverage, baseline 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 the tool retrieves a user's full activity timeline including original tweets and replies. It uses specific verbs 'Get' and 'timeline', and explicitly distinguishes from sibling tool 'twitter_user_tweets' which returns only original tweets.

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 explicit guidance on when to use this tool (to understand community engagement) and when to use the alternative 'twitter_user_tweets'. It also mentions pagination using cursor, helping the agent understand the usage pattern.

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