get_member_roles

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states that the tool retrieves a member's roles, but does not mention any filtering behavior (e.g., adminOnly attributes), permissions required, response format, or whether it returns full role objects or just IDs. This is a minimal disclosure.

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, concise sentence that front-loads the core purpose. It is efficient with no filler or redundant information, making it easy for an agent to parse quickly.

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?

The tool has 5 parameters and no output schema, yet the description does not explain the return structure, the meaning of the boolean filters in practice, or any edge cases. The description alone would leave an agent uncertain about what data is returned and how to use the optional parameters effectively.

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 100% coverage of parameter descriptions, so the baseline is 3. The description itself adds no parameter-level detail (e.g., how 'includeDetails' changes the response), but the schema already provides sufficient semantics for each parameter.

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 specifies the verb '取得' (get) and the resource '特定のDiscordサーバーメンバーのロール一覧' (list of roles for a specific Discord server member), distinguishing it from sibling tools like get_guild_roles (server roles) and get_user_list. It accurately states what the tool does.

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 implies usage context by specifying '特定の' (specific) member, which differentiates it from broader tools like get_guild_roles. However, it does not explicitly state when to use this tool versus alternatives or any exclusions, leaving the distinction to inference.

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