members_get_current_user

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses the two-step API call sequence ('via GET /users/@me followed by GET /guilds/{guild.id}/members/{bot.id}') and the return structure. It also highlights a nuance: 'Structured nick remains raw Discord data; the human-readable text response fences it.' No contradiction with annotations.

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 well-organized with bolded labels, a concise purpose sentence, a bullet-point use case, and a compact returns section. Every sentence contributes useful information without redundancy.

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 simple one-parameter read operation with an output schema, the description covers purpose, when to use, and return fields. It also mentions the intent requirement avoidance, making it fully sufficient for an agent to decide and invoke correctly.

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 already provides 100% coverage of the single parameter with a clear description ('Guild to inspect'). The tool description only refers to 'target guild' generically, adding no new meaning beyond the schema. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Fetch the current bot user's own member entry in a guild.' This clearly distinguishes it from siblings like members_get by focusing on the bot's own membership. The mention of the underlying endpoints further anchors its exact purpose.

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?

A 'When to use' section explains the key scenario: discovering the bot's nick and role assignments without needing the GUILD_MEMBERS intent. However, it does not explicitly name alternatives or state when not to use this tool, so it stops short of full comparative guidance.

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