discord_timeout_member

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

Annotations already indicate not read-only, not destructive, idempotent, and open-world. The description adds essential behavioral details: the specific effects, the ability to clear with 0, the maximum duration, and the required permission. No contradictions 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 three sentences, each informative and necessary. It front-loads the main purpose, then adds the clearing mechanic, duration limit, and permission requirement. No wasted words.

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?

Given no output schema, the description covers the main aspects: purpose, effect, special parameters, limits, and permissions. It lacks error handling details or return value, but the tool is straightforward and the annotations fill safety gaps.

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 coverage is 100%, so baseline is 3. The description adds meaning by explaining the special use of duration_minutes=0 to clear timeouts and the maximum value (40320 minutes). It also clarifies the reason parameter is optional (per the schema). This adds value beyond the schema descriptions.

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 states the tool's purpose: 'Mute a member for a set duration (Discord 'timeout')' and explains the effects (no messages, reactions, speech). It distinguishes itself from siblings like ban or kick by focusing on temporary muting. The special case of clearing timeout with duration=0 further clarifies its scope.

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 provides clear usage context: it's for temporary muting, with a max duration of 28 days and a permission requirement. It does not explicitly contrast with siblings (e.g., when to use timeout vs ban), but the temporary nature is implied.

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