get_list_tweets

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Get tweets' implies a read operation, but there's no information about rate limits, authentication requirements, pagination behavior (though cursor parameter hints at it), error conditions, or what format/quantity of tweets are returned. The description is minimally adequate but lacks important operational context.

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 extremely concise at just 5 words, front-loading the core functionality with zero wasted words. Every word earns its place, making it easy for an agent to quickly understand the basic purpose.

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 that there's an output schema (which handles return values), the description's job is reduced. However, for a tool with 3 parameters (one required), no annotations, and 0% schema coverage, the description should provide more operational context about how the tool behaves and when to use it versus alternatives. The existence of an output schema prevents a lower score, but significant gaps remain.

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?

With 0% schema description coverage for all 3 parameters, the description provides no parameter information whatsoever. It doesn't explain what 'list_id' refers to, what 'count' controls (number of tweets? default behavior?), or what 'cursor' is for (pagination token?). The description fails to compensate for the complete lack of schema documentation.

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 action ('Get tweets') and the resource ('from a list's timeline'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from similar sibling tools like get_timeline, get_user_tweets, or get_latest_timeline, which prevents a perfect score.

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. With multiple tweet-retrieval tools in the sibling list (get_timeline, get_user_tweets, get_latest_timeline, get_conversation, etc.), there's no indication of when this list-specific retrieval is appropriate versus other tweet-fetching methods.

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