ncloud_datacatalog_get_database

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

The description adds that the result includes tags, which supplements the readOnlyHint annotation. However, it does not disclose additional behavioral traits such as rate limits, authentication requirements, or response structure, beyond the minimal context from annotations.

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 with no superfluous words. It is front-loaded and concise, achieving clarity in minimum space.

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?

Given the lack of an output schema, the description should better indicate what 'database detail information' encompasses. While it mentions tags, it does not list other likely fields (e.g., location, owner, creation time). The description is adequate but not fully informative.

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% coverage with descriptions for all three parameters (catalogId, databaseName, includeTags). The description adds slight value by linking 'including tags' to the includeTags parameter, but it does not enhance understanding beyond the schema descriptions.

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 'Get' and resource 'database detail information', and 'including tags' adds specificity. It distinguishes from sibling 'ncloud_datacatalog_get_databases' which lists databases, while this retrieves details for a single database. However, it could explicitly mention that it returns full detail for a specific database.

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 any guidance on when to use this tool versus alternatives like 'ncloud_datacatalog_get_databases' or 'ncloud_datacatalog_get_table'. No context on prerequisites or exclusions.

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