discord_mod_timeout_member

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

The description reveals that the tool performs a timeout (server mute) and explains the clearing behavior with durationSeconds=0. No annotations are provided, so the description carries the full burden. It lacks details on permissions, side effects, or what happens if the user is already timed out, but addresses the core behavior.

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 extremely concise with two sentences, no unnecessary words, and gets straight to the point. It is well-structured with actionable 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?

Given the tool has no output schema and no annotations, the description provides essential behavioral context: what the tool does, how to clear a timeout, and the maximum duration. It is complete enough for a straightforward mutation tool, though it could mention error cases or permissions.

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 covers all parameters with 100% description coverage. The description adds value by emphasizing that durationSeconds=0 clears a timeout, which goes beyond the schema's listing of max duration. Other parameters like guildId, userId, and reason are self-explanatory and need no further elaboration.

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 'Timeout (server mute) a member', specifying the verb and resource. It also explains the special case of clearing a timeout with durationSeconds=0, distinguishing it from other moderation actions like kick or ban.

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 explicitly says to use durationSeconds=0 to clear a timeout, providing clear context for usage. However, it does not mention when not to use this tool or suggest alternatives, though the sibling tools list provides implicit differentiations.

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