get_list_subscribers

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

With no annotations, the description carries the full burden. It implies a read operation (get) and mentions pagination behavior via cursor. However, it does not explicitly state that the tool is read-only, nor does it disclose potential errors, rate limits, or other behavioral traits beyond pagination.

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—three lines with a clear purpose and parameter details. No redundant information, and the purpose is front-loaded.

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 tool has 3 parameters and an output schema, the description covers purpose, pagination, and parameter semantics adequately. It references pagination cursors ('previous response's next_cursor'), which provides necessary context. However, it could mention the output schema or the format of results, though the existence of an output schema reduces the need.

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 0%, so the description fully compensates by explaining each parameter: list_id as the list ID, count with default and max (20, 100), cursor as a pagination token from a previous response. This adds significant meaning beyond the schema's minimal type and default info.

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 subscribers of a Twitter List, with pagination noted. The verb 'Get' and resource 'subscribers of a Twitter List' are specific, and it is distinguishable from sibling tools like get_list_members which likely targets list members rather than subscribers.

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 clear context for using the tool (to retrieve subscribers with pagination), but does not explicitly state when to use it versus alternatives like get_list_members or get_list. No exclusions or alternative suggestions are given.

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