ncloud_add_postgresql_databases

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

The annotation provides destructiveHint: false, but the description adds no behavioral context beyond that. It does not disclose side effects, idempotency, authorization needs, or error scenarios.

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, succinct, but lacks important details. It is appropriately sized but could include key usage context without being verbose.

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 tool has 2 parameters and no output schema, the description is incomplete. It omits that multiple databases can be added in one call and does not mention the requirement for an existing PostgreSQL instance.

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 coverage is 100%, with descriptions for both parameters. The description adds no additional meaning or nuance beyond what the schema already provides.

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 databases to a Cloud DB for PostgreSQL instance'. It specifies the verb and resource, but does not distinguish from sibling tools like ncloud_add_postgresql_users or indicate that multiple databases can be added in one call.

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 offers no guidance on when to use this tool versus alternatives, nor does it mention prerequisites (e.g., the PostgreSQL instance must exist) or scenarios where this tool is inappropriate.

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