ncloud_export_postgresql_log

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

The description says 'Export' which implies writing to Object Storage (a mutation), but the annotations declare readOnlyHint=true. This is a direct contradiction. The description does not clarify the actual behavior (e.g., whether it's asynchronous, permissions needed).

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 wasted words. The purpose is front-loaded, and the usage hint follows immediately.

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?

With contradictory annotations and no output schema, the description should provide more context about the export operation (e.g., synchronous/asynchronous, what happens after export). It is insufficiently complete for a tool with 6 parameters and no output schema.

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%, so the baseline is 3. The description adds value by linking the fileName parameter to the output of the list tool, but does not explain other parameters beyond the schema.

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 ('Export'), the resource ('Cloud DB for PostgreSQL server log file'), and the destination ('Object Storage'). It distinguishes itself from sibling tools like ncloud_export_mysql_log by specifying the database type and referencing the related list tool.

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 explicitly instructs to use ncloud_list_postgresql_logs to get available log files, providing a clear prerequisite. It lacks explicit when-not-to-use or alternative tools, but the context is sufficient for most cases.

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