ncloud_list_mssql_log_files

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

The readOnlyHint annotation already indicates a safe read operation, so the description does not need to repeat that. However, it discloses no further behavioral traits such as pagination, ordering, or what constitutes a log file. With annotations covering the safety profile, a score of 3 is appropriate—adequate but not adding extra context.

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 a single, front-loaded sentence with no wasted words. It efficiently conveys the tool's purpose.

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?

Given the simplicity (one required parameter, readOnly hint, no output schema), the description provides the basic function. However, it omits details about the return format (e.g., file names, sizes, timestamps) which could be useful since there is no output schema. It is minimally acceptable but not fully informative.

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%—the single parameter 'cloudMssqlServerInstanceNo' is described as 'Cloud MSSQL server instance number'. The tool description adds no additional meaning beyond what the schema provides. Baseline 3 is correct.

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 'List log files for a Cloud DB for MSSQL server instance', which is a specific verb (list) and resource (log files) with a clear context (MSSQL server instance). It distinguishes from sibling tools like ncloud_list_mssql_backups (backups) and ncloud_list_mssql_log_backup_files (log backup files) by focusing on 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?

No guidance is provided on when to use this tool versus alternatives like ncloud_list_mssql_backups or ncloud_list_mssql_log_backup_files. The description does not mention use cases, prerequisites, or exclusions, leaving the agent without decision support.

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