remove_list_member

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

No annotations are provided, so the description must fully disclose behavior. It states the removal action and parameter constraint, but lacks details on idempotency, error conditions (e.g., if the user is not a list member), required permissions, or side effects.

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 concise, uses a clear structure with bullet-pointed Args, and front-loads the primary purpose. Every sentence adds value without redundancy.

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's complexity (3 parameters, mutation operation, sibling tools exist), the description is insufficient. It omits key behavioral details like success/failure indications, error handling, and whether the operation is reversible. An output schema exists but does not excuse the lack of behavioral context.

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 adds minimal semantics: it clarifies that screen_name is 'without @' and user_id is 'Twitter numeric user ID.' This adds some value, but the list_id parameter is only described as 'required,' and no format or constraints are given.

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's purpose: 'Remove a user from a Twitter List.' It uses a specific verb and resource, and the action is distinct from sibling tools like 'add_list_member' or 'get_list_members'.

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 includes a constraint: 'Caller must provide exactly one of screen_name / user_id.' However, it does not specify when to use this tool versus alternatives, such as when to block, unfollow, or mute a user instead.

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