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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful behavioral context: newest-first ordering by created_at, cursor-based pagination at roughly 20 tweets per page, and the effect of includeReplies. It does not cover every edge case, such as behavior when both userName and userId are supplied, but with annotations covering the safety profile, this is a strong disclosure.

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 front-loaded with the most critical usage constraint, then moves to the alternative tool, then the core behavior, parameters, and pagination. Every sentence earns its place; there is no filler or repetition of annotations.

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 four well-documented parameters, the description covers invocation, parameter selection, ordering, reply inclusion, and pagination, and names the sibling alternative. Because there is no output schema, it leaves the exact result envelope and field-level response format unspecified, but this is a minor gap for selecting and calling the tool 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?

Schema description coverage is 100%, so the input schema already documents all four parameters thoroughly. The description reinforces the either/or relationship between userName and userId and the preference for userId, but it adds little substantive meaning beyond the schema, matching the baseline for high schema coverage.

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 verb and resource: fetch the most recent tweets posted by a Twitter/X user, sorted newest first. It further distinguishes itself from search_tweets by explicitly limiting scope to 'latest / recent / what's new' queries, so an agent can differentiate it from siblings without inspecting schemas.

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 gives explicit when-to-use and when-not-to-use guidance with concrete examples: DO NOT use for date-range queries, and for those use search_tweets with a 'from:user since:... until:...' query. This is the strongest possible usage routing for an agent.

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