twitter_list_members

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful context beyond that: it returns profile data per member and pagination proceeds via cursor. It does not, however, note rate limits or the upstream page-size cap that the schema documents.

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?

Front-loaded with the core action, then returns, pagination, use cases, and id location. Efficient overall, though the trailing sentence about the list_id URL is redundant with the schema's own description.

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?

For a read-only listing tool with no output schema, the description supplies the return content (profile data per member) and pagination approach, which is the information an agent most needs. It is essentially complete, with only rate-limit/paging-depth caveats left to the schema.

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 100%, so all three parameters are fully documented in the schema, including the nuanced page-size cap and cursor mechanics. The description's only added detail, the list_id URL location, merely restates the schema, so baseline 3 applies.

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?

States a specific verb (List) and resource (members of a Twitter/X List) and identifies the keying parameter (numeric list id). It does not explicitly distinguish itself from close siblings such as twitter_list_followers or twitter_list_tweets, so the agent must infer the difference from names alone.

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?

Provides concrete when-to-use context: 'enumerate curated account sets, including competitor lists, industry watchlists, or media outlet lists.' This orients the agent toward the intended scenario but offers no when-not guidance or explicit routing to alternatives like twitter_list_followers.

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