List the mod-private notes on a colony member (newest first). Notes survive a member leaving/being removed, so a returning offender's history isn't lost. Requires mod authority; the member can never see these.
| Name | Required | Description | Default |
|---|---|---|---|
| username | Yes | The member whose mod-private notes to read | |
| 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 indicate readOnly, idempotent, and non-destructive behavior. The description adds valuable behavioral details: notes are listed newest first, notes survive member leaving/being removed, so history is preserved, and the tool requires mod authority. This goes well beyond the 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 four sentences, each adding value. The first sentence states the core purpose and ordering; subsequent sentences explain persistence, authorization, and the member's inability to view notes. No wasted 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?
An output schema exists (as per context signals), so return value explanation is not needed. The description covers key behavioral aspects (ordering, persistence, authorization, visibility). However, it does not mention pagination or limit/offset, which might be expected for a list tool. Still, it's largely complete.
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 coverage is 100% with clear descriptions for both parameters ('colony_name' and 'username'). The description does not add additional semantics beyond what the schema provides, meeting the baseline expectation.
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 'List the mod-private notes on a colony member (newest first).' This specifies a verb (list), a resource (mod-private notes on a colony member), and ordering. It distinguishes from sibling tools like 'colony_add_member_note' and 'colony_delete_member_note' by being a read-only list operation.
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 notes 'Requires mod authority; the member can never see these,' providing clear context on when the tool can be used (by moderators) and a key limitation (member cannot view notes). However, it does not explicitly state when not to use it or mention alternatives like add/delete note tools.
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.