write_mysql_migration_tool

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

No annotations provided. The description indicates file creation but lacks details on side effects, permissions, error handling, or consequences of overwriting.

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?

Single sentence, no redundancy. However, it is in Chinese and could be more structured (e.g., listing purpose, parameters).

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?

Despite having an output schema, the description does not explain return values or success/failure indicators. For a file-writing mutation tool, more context is needed.

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 description coverage is 0%. The description only implies meaning for migration_name and sql_content via 'Laravel-style filenames' and 'SQL structure', but overwrite and workspace_root are unexplained.

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 ('write') and resource ('SQL migration file'), specifies the target directory ('sql/mysql/migrations') and naming style ('Laravel-style filenames'), distinguishing it from siblings that generate SQL or scaffold code.

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?

No guidance on when to use this tool versus alternatives like generate_codegen_sql_tool. No prerequisites or exclusion criteria are mentioned.

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