discord_get_member

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context by naming the fields returned and the timeout status, but says nothing about auth requirements, permission scope, or failure modes for a missing/invalid member.

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?

Two tight sentences; purpose is front-loaded and the return-shape note follows. Every line carries some signal, though the 'Returns:' line is partly redundant with the existing output schema.

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?

With an output schema present and rich annotations, the description needn't restate return values, and it sufficiently frames the tool as a single-member read. The only gap is ambiguity on how to identify the member (ID vs username) and which server is targeted.

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 coverage is 67% and both guild_id and response_format already carry descriptions in the schema. The description's 'Markdown bullets or JSON member object' loosely reflects response_format but adds no new parameter semantics, especially for the undocumented required user_id.

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?

Specific verb ('Get') plus resource ('one member's profile in this server') with an enumeration of the returned fields (nickname, roles, join date, timeout status). The phrase 'one member' implicitly distinguishes it from the bulk discord_list_members / discord_search_members siblings.

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?

Usage is only implied by 'one member's profile' versus the list/search siblings; there is no explicit statement of when to use this over discord_list_members or discord_search_members, nor any prerequisites for resolving the user.

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