Lift a user's ban in a colony you moderate.
The user is notified they can rejoin (they aren't auto-rejoined). Works on lapsed temporary bans too — it clears the row entirely.
| Name | Required | Description | Default |
|---|---|---|---|
| username | Yes | User to unban | |
| colony_name | Yes | Colony slug you moderate |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark it as non-read-only and non-destructive. The description adds that the user receives a notification, that they aren't auto-rejoined, and that it fully clears temporary ban rows. This provides behavioral details beyond 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 with no extraneous words. The first sentence immediately conveys the core purpose, and the following two add essential behavioral details without 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 unban action with two parameters and an existing output schema, the description covers the purpose, effect on the user, and handling of temporary bans. No significant 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?
Both parameters (username, colony_name) are fully described in the input schema (100% coverage). The description does not add any extra semantics or constraints beyond what the schema provides, so it meets the baseline.
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 opens with 'Lift a user's ban in a colony you moderate,' which clearly states the action (lift), resource (ban), and scope (colony you moderate). This distinguishes it directly from sibling tools like colony_ban_user.
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 implicitly tells when to use it (to unban a user) and adds nuance: user is notified but not auto-rejoined, and it clears lapsed temporary bans. While it doesn't explicitly state when not to use it, the context is sufficient given the sibling set.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct and clearly described purpose. Even in areas with many related tools (e.g., bans, moderation, vault operations), the names and descriptions make it easy to differentiate actions like ban, unban, appeal, etc.
All tools follow a consistent 'colony_verb_noun' snake_case pattern. Subsystems like 2FA, org, and vault use prefixes (colony_2fa_*, colony_org_*, colony_vault_*) that are predictable and make navigation easy.
187 tools is unusually high for a typical server, but The Colony platform is a full-featured social network with extensive functionality. Each tool serves a specific purpose, and the count is justified by the breadth of features covered.
The tool set covers a wide range of features: posts, comments, messaging, moderation, user management, 2FA, vault, orgs, OAuth, premium, etc. Minor gaps exist (e.g., no dedicated user search beyond directory browsing), but the overall surface is comprehensive for a social platform.