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

The description discloses pagination behavior (using cursor and count) and billing cost (1 credit per call), which are important. However, it omits other behavioral aspects like authentication requirements, potential rate limits, or that it returns only public tweets. Without annotations, the description carries the full burden but only partially covers these traits.

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 exceptionally concise, using only two sentences to convey the primary function and key usage hints. It avoids redundancy and fluff, making it easy for an agent to parse quickly.

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?

While the description covers the basic function and pagination, it does not explicitly state that it returns tweets for a specific user (relying on the title and parameter names). It also omits any preconditions or error scenarios. Given the presence of a schema with parameter descriptions, the text is sufficient for basic usage but lacks completeness for edge cases.

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 only mentions cursor and count for navigation, which is already described in the schema. It does not add any extra meaning for the userId or username parameters, nor does it clarify the relationship between them beyond what the schema states. The description adds negligible value over the parameter descriptions.

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 all tweets ordered by most recent, which indicates a read operation. It distinguishes from sibling tools that handle followers, media, etc., but it does not explicitly mention that it's for a specific user, though the title and parameter imply it.

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 guidance on when to use this tool versus alternatives. It only mentions pagination via cursor and count, but does not explain scenarios such as fetching a user's timeline or when to prefer this over search or other get_user tools. No comparison with alternatives is given.

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