Remove timeout

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

Annotations already declare non-readOnly and non-destructive, and the description adds a temporal qualifier ('early') but does not mention permission requirements or behavior when no timeout exists. It adds some value beyond annotations but lacks depth expected for a state-changing tool.

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?

Single eight-word sentence, front-loaded with the action ('Lift'), with zero fluff or repetition.

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?

For a simple three-parameter mutation tool with annotations, the essential purpose is clear. It does not address edge cases (e.g., no active timeout) but those are not critical given the tool's simplicity and the schema.

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 covers guild and member with descriptions, but reason is undocumented (67% coverage). The description provides no parameter-specific guidance and does not compensate for the missing reason parameter.

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 uses the specific verb 'Lift' and clearly identifies the resource ('active timeout') and target ('member'). It unambiguously distinguishes this from timeout_member, which sets a timeout, and from other moderation actions.

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 implies usage when an active timeout needs to be ended early. It does not explicitly name alternatives or exclusion cases, but the contrast with timeout_member is implicit from the verb 'lift' and the sibling toolset.

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