ncloud_export_mssql_log

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

The description uses 'Export' which implies a write operation (creating objects in Object Storage), contradicting the annotation readOnlyHint: true. This is a serious inconsistency. No additional behavioral traits are disclosed beyond this contradiction.

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 the main purpose and a usage hint. No redundant words. Every sentence adds value.

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?

While the description is minimal, it covers the essential action and a useful companion tool. However, given the tool has 5 parameters and no output schema, more context about the export process or behavior would improve completeness. The description does not differentiate from sibling export tools beyond the MSSQL log scope.

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% (all 5 parameters described in schema). The description adds no extra parameter meaning beyond what the schema already provides, so baseline score 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 clearly states the tool's purpose: 'Export Cloud DB for MSSQL server logs to Object Storage.' It specifies the verb (Export), resource (logs), and target (Object Storage). It also distinguishes from siblings by referencing a specific companion tool for listing log files.

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 advises using ncloud_list_mssql_log_files to get available log files before export, providing clear context for when to use this tool. However, it does not mention when not to use it or provide alternatives among sibling export tools.

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