get_list_tweets

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

With no annotations provided, the description carries the full burden of disclosing behavior. It does mention pagination via cursor, adding useful behavioral context, but it does not explicitly state side-effect safety, authentication requirements, or rate limits. For a read-only getter, this is acceptable but not comprehensive.

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 compact and well-structured, front-loading the main purpose in a single sentence followed by a clear Args list. Every line adds value with no redundant filler.

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?

The tool is simple and the description covers all parameters and the key pagination behavior. The presence of an output schema means return values need not be described. However, it lacks explicit guidance on when to use this instead of other tweet-fetching tools, so it is not fully complete.

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 has 0% description coverage, so the description provides all parameter meaning. It explains list_id as the list ID, count with default (20) and max (100), and cursor as a pagination token from a previous response's `next_cursor`. This goes well beyond the bare schema definitions.

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 'Get' and the resource 'tweets from a Twitter List', which precisely defines the tool's purpose. This distinguishes it from sibling tools like get_list or get_list_members, which operate on list metadata or members, not 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 implies usage through its straightforward verb-noun structure, but it does not explicitly provide alternative tools or when-not-to-use scenarios. Sibling tools like get_timeline or get_user_tweets are not mentioned, leaving the agent to infer when list tweets are preferable.

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