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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral detail beyond that: page size limit, cursor pagination, and the returning fields `has_next_page` and `next_cursor`. It does not discuss rate limits or auth, but the annotation coverage lowers the burden.

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?

Three dense sentences with no wasted words: purpose and pagination, use case and rationale, return fields, and related sibling tool. Information is front-loaded and every sentence earns its place.

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 output schema exists, annotations cover the safety profile, and the description covers pagination, return fields, and a related tool, nothing essential is missing for an agent to select and invoke this 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 coverage is 100%, so the schema already documents both parameters. The description still adds value by explaining pagination behavior tied to the `cursor` parameter and clarifying that results are limited to 20 per page. It does not fully describe cursor format, but it supplements the schema meaningfully.

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 states a specific action and resource: 'Get the tweet timeline of an X List by listId'. It also adds concrete characteristics such as 'up to 20 per page, cursor-paginated', which makes the tool's scope clear and distinguishes it from related timeline/list tools.

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 gives clear when-to-use context: monitor a hand-curated set of accounts as a single feed, framing Lists as the cheapest way to track a fixed cohort. It names one alternative explicitly ('To see who is in the List use get_twitter_list_members'), though it does not explicitly contrast with alternatives like the single-user tweet timeline.

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