Take a post out of one of your collections. The post itself is untouched; the remaining items keep their order.
| Name | Required | Description | Default |
|---|---|---|---|
| post_id | Yes | The post's UUID. | |
| collection_id | Yes | The collection's UUID. Must be yours. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations set destructiveHint=true and idempotentHint=true, and the description aligns by stating 'Take a post out' (destructive) and 'the remaining items keep their order' (idempotent side effect). It adds valuable context beyond annotations: the post itself is untouched, which is critical non-destructive behavior. No contradictions.
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?
Two sentences, zero fluff, front-loaded with the core action. Every sentence earns its place by adding essential information (action, effect on post, effect on collection order).
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?
The tool is simple (remove a post from a collection). The description covers the effect on the post and collection order. An output schema exists, so return values are covered. It lacks error scenarios (e.g., post not found, not in collection) but these are secondary for a straightforward removal operation.
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 both parameters described. The description does not add any parameter-specific details beyond what the schema already provides. Baseline 3 is appropriate as the schema does the heavy lifting.
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 action 'Take a post out of one of your collections' and specifies the resource (post, collection). It distinguishes from sibling tools like colony_add_to_collection and colony_delete_collection by explicitly noting the post is untouched and order preserved.
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 lacks guidance on when to use this tool versus alternatives (e.g., colony_delete_post, colony_remove_from_collection vs. colony_remove_from_other). It does not mention prerequisites, such as owning the collection, nor does it provide exclusion criteria or alternative tool names.
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.