ncloud_datacatalog_update_database

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

Annotations already provide idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the scoping detail that only location and/or description are updated, but it doesn't disclose behaviors like whether unspecified fields are left untouched or what happens if neither optional field is provided.

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?

Two sentences with no filler. The main purpose is front-loaded, and the sibling routing sentence earns its place by preventing misuse for tag updates.

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 simple update operation, the combination of a strong schema, clear annotations, and a scoped description is mostly complete. A minor gap is that the description doesn't explicitly say at least one of location or description should be supplied, though 'and/or' strongly implies it.

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 100%, with each parameter already well-described, including the max length for description and the source for databaseName. The description adds no parameter-level detail beyond what the schema already provides, so the baseline of 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 uses a specific verb and resource: 'Update a database's location and/or description.' It also names the exact sibling for tag updates, ncloud_datacatalog_update_database_tag, so the tool's scope is immediately distinguishable from related tools.

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 clearly states what the tool updates and explicitly routes tag management to a separate sibling tool. It doesn't enumerate broader when-to-use or when-not-to-use scenarios, but the main alternative is covered directly.

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