discord_timeout_user

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

With no annotations provided, the description carries the full burden and effectively discloses key behavioral traits: it specifies the action is a timeout (not read-only), mentions the 28-day maximum duration, explains how to clear a timeout, and states the required permission. It lacks details on error handling or response format, but covers essential operational context.

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 front-loaded with the core purpose, followed by key details in a logical flow: effects, duration, special case, and permission requirement. Every sentence adds value with no wasted words, making it highly efficient and easy to parse.

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 annotations and no output schema, the description does well by covering purpose, usage, key parameters, and permissions. It could improve by mentioning error cases or response structure, but it's largely complete for a mutation tool with moderate complexity.

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 low at 25%, but the description adds significant meaning: it explains that duration_seconds=0 clears a timeout and notes the 28-day max, which clarifies beyond the schema's basic description. It doesn't detail guild_id or user_id semantics, but compensates well for the coverage 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?

The description clearly states the specific action ('Timeout a user') and the effects ('they cannot send messages, react, or join voice'), distinguishing it from sibling tools like discord_kick_user or discord_remove_role by specifying timeout functionality rather than removal or role management.

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?

It provides explicit guidance on when to use this tool ('Timeout a user') and when not to (e.g., for removal use discord_kick_user), including prerequisites ('Requires Moderate Members permission') and special cases ('Pass duration_seconds=0 to remove an existing timeout').

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