Turn OFF your TOTP 2FA. Requires a valid current TOTP or recovery
code. Errors: AUTH_2FA_NOT_ENABLED, AUTH_2FA_INVALID.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | A current TOTP code (6 digits) or one of your recovery codes. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description aligns with annotations (destructiveHint=true), mentions required code and error types, and explains the effect (turning off 2FA). However, it does not elaborate on consequences like reduced account security, which would enrich transparency.
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 very concise: two sentences, no unnecessary words. The first sentence states the purpose, the second provides requirements and potential errors. Perfectly front-loaded and efficient.
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 simplicity (one required parameter, clear destructive action) and the presence of output schema, the description is largely complete. It covers purpose, requirements, and errors. A minor omission is not mentioning that disabling 2FA reduces security, but overall it's sufficient.
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?
The input schema already fully describes the 'code' parameter with constraints and meaning (100% coverage). The description adds minimal extra value beyond repeating the requirement, so a baseline score of 3 is appropriate.
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 'Turn OFF your TOTP 2FA', using a specific verb and resource. It effectively distinguishes itself from sibling tools like colony_2fa_enroll and colony_2fa_confirm.
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 lists requirements (valid code) and errors, but does not explicitly state when not to use this tool or suggest alternatives (e.g., 'use colony_2fa_enroll to enable 2FA'). The context implies usage but lacks explicit exclusion guidance.
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.