discord_delete_thread_member

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description still adds real value beyond that: the authorization paths (Manage Threads vs. private-thread creator), the archived-thread precondition, and the exact-change approval prompt before execution. It stops short of covering failure modes such as the target user not being a 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?

Front-loaded with the action, then preconditions, then sibling routing in a single dense sentence chain. It loses a point for redundancy: the trailing 'Bot permissions it may need: Manage Threads' repeats the permission already stated earlier in the same sentence.

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-parameter mutation tool with an output schema, the description covers everything an agent needs before calling: what it does, what permission is required, what state blocks it, what confirmation the user will see, and which sibling handles the adjacent intents.

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 carry their own descriptions and numeric-ID patterns, so the schema does the heavy lifting. The description reinforces that user_id means the person removed and channel_id means the thread, but adds no format or ID-resolution guidance beyond the schema.

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 ('Remove another user from a thread by user ID') and immediately distinguishes the action from its nearest siblings, discord_leave_thread and discord_add_thread_member. The word 'another' alone rules out the self-removal case that a sibling covers.

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?

Names both alternatives explicitly with the condition that selects each: use discord_leave_thread for the bot to leave, discord_add_thread_member to add. It also gives the preconditions for using this tool (Manage Threads or being creator of a private thread, and the thread must not be archived).

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