migrate_bot_storage

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

With no annotations, the description carries full burden. It discloses dry-run capability and the existence of options like overwrite and deleteSource, but omits side effects, permissions required, or irreversibility. It adds some context beyond the schema but not enough for a complete behavioral picture.

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 concise with three sentences: purpose, dry-run support, and option list. No wasted words, front-loaded with key action.

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 5-parameter migration tool with no output schema, the description lacks detail on what 'db.xx storage' is, the migration process's effects on existing data, and expected return value. It covers the basics but leaves gaps that could confuse an AI agent.

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 description lists all parameters but does not add semantic meaning beyond the schema. Schema coverage is 60% (bowser?, overwrite undocumented). The enumeration helps but does not explain purposes or constraints like the meaning of 'scope' values or 'overwrite' behavior.

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 verb 'Migrate' and identifies the specific resource transition ('sync Bot.setProp data to async db.xx storage'). It also lists key options, distinguishing it from siblings like clear_bot_storage or get_bot_storage_keys.

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 does not provide explicit guidance on when to use this tool versus alternatives. It mentions dry-run preview but offers no when-not or context for choosing migration over other operations like clearing or reading storage.

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