ncloud_export_mysql_log

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

The annotation readOnlyHint=true indicates no state changes, but the description says 'Export... to Object Storage,' which implies a write operation. This is a direct contradiction, scoring 1 per the rubric.

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, zero fluff, front-loaded with the action. Very concise and well-organized.

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 omits return value semantics (no output schema) and does not mention whether the export is asynchronous or requires special permissions. Combined with the annotation contradiction, the description is not complete enough for a 6-parameter side-effecting tool.

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 6 parameters. The description adds a pointer to ncloud_list_mysql_logs for obtaining the fileName, providing minimal additional context beyond the schema. 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 a specific verb ('Export'), the resource ('Cloud DB for MySQL server log file'), and destination ('Object Storage'). It distinguishes from sibling export tools for other DB types (e.g., ncloud_export_postgresql_log) by specifying MySQL.

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 directs the user to use ncloud_list_mysql_logs to discover available log files, providing a clear prerequisite and usage hint. It does not, however, explain when to avoid this tool or discuss alternative export methods, but the context is otherwise clear.

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