discord_get_member_info

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's 'Read-only' line adds nothing, and 'Returns a JSON object' is trivial given an output schema exists. The field enumeration (roles, effective permissions, timeout status) is genuinely useful context for what the call surfaces, but nothing is said about permissions required to view members or when the call fails (e.g. member not in guild).

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?

Three short sentences, front-loaded with the payload contents. 'Read-only. Returns a JSON object.' is largely redundant against the annotations and output schema, so not every sentence earns its place, but there is no bloat.

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?

For a two-param read tool with full schema coverage, annotations, and an output schema, the definition covers what the call returns well enough to invoke correctly. The remaining gap is failure/permission context, which is minor relative to the rich structured metadata.

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 both parameters (user_id, guild_id) are documented as snowflakes in the schema, so baseline 3 applies. The description adds no meaning beyond the schema – it never reinforces that both IDs are required to scope the lookup.

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?

States a specific verb and resource ('Get full details for one server member') and enumerates the payload ('roles, effective permissions, account/join dates, bot flag, and current timeout status'). The 'one member' framing cleanly separates it from discord_list_members and discord_search_members without needing to name them.

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 the phrase 'for one server member' – there is no explicit when-to-use, no mention of prerequisites (e.g. intents or permissions needed to read a member), and no routing to the list/search siblings for bulk lookups. An agent can infer the single-member case but is given no exclusions.

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