timeout_member

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

The description discloses the maximum duration and the removal behavior, which are key behavioral details. However, it omits other aspects like required permissions, side effects on existing timeouts, or return values. With no annotations, the description carries the full burden but only partially meets it.

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, using two sentences to convey the action, boundary condition, and special case. No unnecessary words, and the critical info is front-loaded.

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's simplicity (3 required params, no output schema, no annotations), the description covers the core function and important edge cases (max duration, removal). It lacks parameter semantics for two params but is otherwise complete for a mutation tool of this 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?

The schema has 0% coverage (no parameter descriptions). The description adds meaning only to duration_seconds (max, removal case), leaving user_id and guild_id completely unexplained. Thus it provides partial compensation but is insufficient for low coverage.

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 verb 'timeout' and the resource 'member', and specifies the duration parameter with a maximum value and the removal case via 0. This effectively distinguishes it from sibling tools like kick_member or ban_member.

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 explains the behavior for duration_seconds (max 28 days and pass 0 to remove), which provides some usage context. However, it does not explicitly state when to use this tool over alternatives or mention any prerequisites or exclusions.

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