Migrate a basic group to a supergroup

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate destructive behavior (destructiveHint=true), but the description adds 'one-way migration' clarifying irreversibility and mentions the return of the new supergroup id in updates. This goes beyond the annotations, though it does not elaborate on side effects like message loss or permission changes.

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 two short sentences, front-loaded with the key concept 'One-way migration', and includes the output expectation. Every word adds value with no redundancy.

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 destructive mutation tool with no output schema and incomplete parameter coverage, the description is too sparse. It explains the return value vaguely ('resulting updates') but does not cover prerequisites, effects on the original group, or the optional accountId, leaving significant operational context unspecified.

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?

With only 50% of parameters described in the schema (chatId yes, accountId no), the description should compensate but does not. It adds no explanation of accountId or any parameter details, leaving a gap in understanding required for correct invocation.

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 title and description clearly state the tool migrates a basic group to a supergroup. The description adds 'One-way migration' and specifies the result (new supergroup id in updates), making the purpose unambiguous and distinct from any sibling tool.

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 implies use when converting a basic group to a supergroup, and 'one-way' hints at irreversible action. However, it provides no explicit guidance on when to use vs alternatives or any exclusions, leaving context to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.