ncloud_list_mysql_instances

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

The description mentions 'List', which aligns with the readOnlyHint annotation. However, it does not disclose pagination behavior, rate limits, or data freshness. Since annotations already declare read-only, the description adds only the region scoping, which is minimal extra behavioral 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 sentence of 9 words, containing only essential information. It is front-loaded and every word contributes to the 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?

Despite having no output schema, the description does not explain what the response contains (e.g., list format, fields). It also ignores the 4 optional parameters (pagination and filters) which are not trivial. The description is too minimal for a list tool with multiple parameters and no output schema.

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% for all 4 parameters, so the baseline is 3. The description adds no additional parameter meaning beyond what is already in the schema (e.g., no explanation of how pagination or filtering works).

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 verb 'List' and the resource 'Cloud DB for MySQL instances', specifying the scope 'in the current region'. It is specific and unambiguous, though it does not distinguish from sibling list tools for MySQL (e.g., databases, users).

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. Among siblings, there are many MySQL list tools (e.g., ncloud_list_mysql_databases, ncloud_list_mysql_users). The description does not help an agent decide which to choose.

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