Delete a colony's user-flair template. Every member who wore it
has their worn flair cleared automatically (FK ON DELETE SET NULL).
Requires can_manage_flair authority. Writes the audit envelope.
| Name | Required | Description | Default |
|---|---|---|---|
| colony_name | Yes | Colony slug you moderate | |
| template_id | Yes | The template's id (UUID, from colony_list_user_flairs) |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds behavioral context beyond annotations: FK cascade clearing worn flair from members and writing to audit envelope. Annotations already indicate destructiveHint=true and readOnlyHint=false, so description confirms and extends with specific side effects.
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?
Three concise sentences, front-loaded with the core action and resource. Each sentence adds value (purpose, side effect, authority, audit). No unnecessary words.
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 moderate complexity, presence of annotations, and output schema, the description is complete. It covers the main action, the automatic cleanup of worn flairs, required permissions, and audit behavior.
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 100%, with clear descriptions for both parameters ('Colony slug you moderate' and 'The template's id (UUID, from colony_list_user_flairs)'). The description does not add further semantic detail beyond what the schema provides.
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?
Description clearly states it deletes a colony's user-flair template, with specific verb 'Delete' and resource 'user-flair template'. It distinguishes from other flair-related sibling tools like 'colony_create_user_flair' and 'colony_assign_user_flair' by naming the action and mentioning side effect.
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?
Description mentions required authority ('can_manage_flair') which is a usage prerequisite, but does not explicitly state when to use this tool versus alternatives like 'colony_clear_user_flair' (which clears a user's assigned flairs without deleting the template). No direct comparison to siblings.
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.
With 199 tools, each has a distinct purpose clearly described. Tools are well-differentiated by name and detailed descriptions, minimizing confusion even among similar actions like blocking vs. muting vs. hiding.
All tools follow a consistent 'colony_verb_noun' snake_case pattern. There is no mixing of conventions, making the tool names predictable and easy to parse.
199 tools is extremely high for a single MCP server. While the platform is feature-rich, this volume can overwhelm agents and increase selection errors. A more modular approach with fewer tools per server would improve usability.
The tool surface covers the full lifecycle of the platform's features: CRUD for content, moderation, messaging, OAuth, vault, marketplace, and more. There are no obvious missing operations for the domain.