ncloud_export_mssql_backup

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

The description describes a write operation ('Export... backup files'), but the annotations declare readOnlyHint=true, creating a direct contradiction. No additional behavioral details are provided beyond this misleading information.

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 convey the core purpose and a crucial usage hint with no unnecessary words. The structure is efficient and front-loaded.

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 description covers the main action and provides a reference for prerequisite information. However, the annotation contradiction undermines trust and completeness, as the readOnlyHint contradicts the described write operation.

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 all parameters. The tool description adds no extra meaning beyond what is in the schema, so baseline 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 exports MSSQL backup files to Object Storage, using a specific verb and resource. It distinguishes itself by referencing a sibling tool for getting file names, clarifying its role.

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 provides explicit guidance by suggesting the use of ncloud_list_mssql_backup_details to obtain available file names. While it does not explicitly state when not to use or list alternatives, the hint is valuable for correct usage.

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