discord_timeout_member

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

Annotations already mark this as a non-read-only, idempotent, non-destructive open-world mutation, so the safety profile is covered. The description adds real value beyond them: the required permission level, a human-confirmation requirement, and the shape of the confirmation returned. It omits failure behavior (e.g. target above the bot's role hierarchy), keeping it short of a 5.

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 lines: purpose and duration bound first, lift semantics second, permission/confirmation third, return value last. No filler sentences and every line carries information.

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?

An output schema exists, so return values need only a pointer, which the description provides. Permissions, confirmation, mutation semantics and the lift case are all covered; only error/edge-case behavior is absent, which is a minor gap for a 4-parameter tool.

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 75%, with minutes, reason and guild_id already documented in the schema, including the 0-lifts-timeout and 40320-max semantics the description repeats. user_id has only a pattern and no prose in either place, so the description does not compensate for the remaining gap.

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 (time out), the target resource (a member), the concrete effects (no posting, reacting or voice), the duration bound, and the inverse operation (minutes=0 lifts). An agent can distinguish this from discord_kick_member and discord_ban_member purely from the described effect.

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?

Gives a prerequisite (Needs Moderate Members) and an explicit behavioral instruction to confirm with the user before applying, plus the lift-a-timeout case. It does not name the moderation siblings it should be chosen over, but the when-to-use context is clear.

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