ncloud_add_mysql_databases

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

Annotations already declare destructiveHint=false, indicating a non-destructive mutation. The description ('Add databases') aligns with this but adds no further behavioral details (e.g., idempotency, error handling). Since annotations cover the safety profile, the description provides minimal extra value beyond confirming the operation.

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 sentence that efficiently conveys the tool's purpose. No fluff or redundant information.

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 tool with only two parameters and no output schema, the description is minimal. It omits typical contextual details like return values (e.g., success indicator, list of created databases), error conditions, or prerequisites. While the tool is simple, the lack of output information is a gap.

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 has 100% description coverage, clearly defining the two parameters. The description does not add meaning beyond the schema's parameter descriptions ('Cloud MySQL instance number', 'List of database names to add'). Baseline 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 the action ('Add') and the resource ('databases to a Cloud DB for MySQL instance'). It distinguishes from sibling tools like list_mysql_databases, delete_mysql_databases, and add_mysql_users.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as needing an existing MySQL instance, or suggest when to use add_mysql_databases versus other MySQL management tools like add_mysql_users.

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