ncloud_export_postgresql_log

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

Annotations include readOnlyHint=true, so the description's job is to add context. It discloses destination ('Object Storage') but does not mention whether the bucket must exist, whether overwrites occur, or response/async behavior. No contradiction with 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?

Two sentences, front-loaded with action and resource, and includes a helpful pointer to prerequisite tool. No redundant phrasing.

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 no output schema, description should explain what the tool returns. It does not. It also doesn't discuss prerequisites (bucket existence, permissions) or whether the operation is asynchronous. However, readOnlyHint and schema cover much of the context, making it adequate but not complete.

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 has 100% description coverage; all six parameters are described. The description adds no parameter details beyond the schema, only reiterates that fileName comes from ncloud_list_postgresql_logs. Baseline 3 applies.

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?

Specific verb 'Export' + resource 'Cloud DB for PostgreSQL server log file' + destination 'Object Storage'. Distinguishes from sibling export tools (export_mysql_log, export_postgresql_backup) by explicit resource and target.

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?

States prerequisite: use ncloud_list_postgresql_logs to obtain log files. Does not explicitly exclude alternatives (e.g., ncloud_export_postgresql_backup), but gives clear context for its intended purpose.

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