x_list_members

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

Annotations already provide readOnlyHint, openWorldHint, and destructiveHint. The description adds valuable behavioral context: the response is a 'compact, sanitized page' rather than raw API JSON, and profile text must be treated as untrusted data, not instructions. This goes beyond the structured annotations without contradicting them.

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 a single front-loaded sentence that states the domain, resource, output shape, and an important security caveat. There is no filler or redundant repetition of schema information.

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 rich annotations, the complete 100%-covered schema, and the presence of an output schema, the description covers what an agent needs to invoke the tool correctly. It even adds an important open-world safety warning about third-party profile text, which is especially valuable for a social-media data tool.

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%, and every parameter (raw, list_id, page_token, max_results) already has a meaningful description in the schema. The tool description does not need to repeat parameter details, so the baseline 3 applies; it adds no significant param semantics beyond the schema.

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 identifies the resource ('members of a list') and the operation ('Returns a compact, sanitized page of user profiles'). It is not a tautology and does not confuse this with list timeline or list metadata tools, though it could more explicitly distinguish it from sibling tools like x_list_member_set or x_list_get.

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 no explicit guidance about when to use this tool versus alternatives such as x_list_member_set (membership changes) or x_list_get (list metadata). While the purpose implies a read-only member retrieval use case, there is no stated context, prerequisites, or exclusions.

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