discord_members

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

With no annotations provided, the description carries the disclosure burden. It does reveal a behavioral trait by noting that bulk listing may require a privileged intent, which is useful. However, it omits other behavioral details such as return format, pagination behavior, or error handling, so transparency is partial.

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: two short sentences with no filler. The first sentence states the core action, and the second adds a single important caveat. Every word 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?

Despite having 4 parameters and no output schema, the description is minimal. It lacks details about listing pagination (after), response shape, and edge cases like missing userId or limit behavior. This leaves the agent under-informed for a non-trivial list operation.

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 input schema has 0% description coverage, so the description must add parameter meaning. It hints at two modes: 'one member' likely corresponds to userId, and 'list members' relates to after/limit. However, it does not explain the required guildId or the pagination semantics of 'after', leaving gaps.

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 action: 'Get one member or list members.' This is a specific verb+resource combination that conveys the core purpose. However, it does not explicitly differentiate from sibling tools like discord_member_roles or discord_moderate_member, so it is not a 5.

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 a contextual prerequisite for bulk listing ('may require the Guild Members privileged intent'), but it does not specify when to use this tool over alternatives or exclude when to use other member-related tools. The usage guidance is implied rather than explicit.

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