ncloud_export_mssql_log

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

The annotation readOnlyHint=true already signals that the operation is safe from a mutation perspective. The description adds that it exports to Object Storage, which implies a copy operation, but does not disclose potential side effects like storage costs, overwrite behavior, or whether it is synchronous/asynchronous. With annotations covering the safety profile, this level of added context is adequate but not rich.

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 extremely concise: two sentences. The first sentence states the purpose and destination, the second provides a cross-reference to the prerequisite listing tool. Every word earns its place, with no fluff or repetition of schema information.

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?

The tool has no output schema, but it is a focused export operation with well-documented parameters and a clear prerequisite reference. The description covers the main action and directs the user to obtain the required log file list. It does not describe the return format or how to monitor progress, but given the simplicity and strong schema coverage, it is reasonably 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 description coverage is 100%, and all parameters have clear descriptions such as 'Object Storage bucket name to export to' and 'Full object name of the log file to export.' The description does not add extra meaning beyond the schema, but since the schema is comprehensive, a 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 action: 'Export Cloud DB for MSSQL server logs to Object Storage.' The verb 'export' plus the resource 'Cloud DB for MSSQL server logs' and destination 'Object Storage' make the purpose unmistakable. It also distinguishes from sibling tools like export backups by specifying 'logs' and references 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 gives explicit usage context by stating 'Use ncloud_list_mssql_log_files to get available log files.' This tells the agent a key prerequisite and guides it toward the correct companion tool. However, it does not explicitly mention alternatives (e.g., export backups for backups) or provide exclusions, so it stops short of a full 5.

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