ncloud_add_mysql_databases

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

The annotation destructiveHint=false already indicates the operation is non-destructive, and the description adds no additional behavioral context. It does not mention potential failure conditions, idempotency, or any side effects beyond the simple addition of databases. The description is consistent with the annotation but does not enrich it.

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 a single concise sentence that directly states the tool's action and target. There is no redundant or extraneous information, and it is appropriately sized for the tool's simplicity.

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 and has full schema coverage for inputs, but there is no output schema and the description does not explain what the response conveys (e.g., status or job details). It also does not mention constraints like duplicate database names or instance state requirements. The description is minimally sufficient but leaves some gaps for a fully informed 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 input schema provides full descriptions for both parameters (100% coverage), so the description does not need to compensate. The description itself adds no parameter-level detail, and the schema already explains that cloudMysqlInstanceNo is the instance number and cloudMysqlDatabaseNameList is the list of database names.

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 uses a specific verb 'Add' with a clear resource ('databases') and target ('Cloud DB for MySQL instance'), making the tool's purpose unambiguous. It naturally distinguishes itself from sibling tools like ncloud_delete_mysql_databases and ncloud_list_mysql_databases through the additive action.

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 usage (when you need to add databases to a MySQL instance) but provides no explicit context about when to choose this tool over alternatives, nor does it mention any prerequisites or exclusions. It is minimally adequate but lacks the comparative guidance seen in stronger examples.

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