discord_get_member

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

The verb 'Gets' clearly implies a read-only operation, providing basic transparency. However, with no annotations and no mention of failure modes or response shape, the description carries the full burden and reveals only minimal behavioral detail.

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, clear sentence with no redundancy or irrelevant information. It is efficiently structured and easy to parse.

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 there is no output schema and no annotations, the description is too sparse to be fully self-contained. It lacks parameter explanations and any guidance on when to use this tool, making it insufficient for an agent to invoke confidently with correct and complete 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 input schema has no descriptions for guildId or userId, and the description does not explain the parameters. It refers to 'a specific member in a Discord server,' but does not explicitly map guildId to the server and userId to the member, leaving inference to the reader.

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 uses the clear verb 'Gets' and identifies the resource as 'detailed information about a specific member in a Discord server.' It stands apart from sibling tools like discord_list_members and discord_get_server_info, though 'detailed information' is somewhat vague.

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?

There is no guidance on when to use this tool over alternatives such as discord_list_members. The description does not indicate conditions for selecting this member-specific lookup.

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