ncloud_list_route_tables

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

The description adds the scope 'in current region' beyond the readOnlyHint annotation. However, it does not disclose other behavioral traits such as pagination, rate limits, or whether it returns all route tables or only a subset. The readOnlyHint already signals safety, so the additional region context is helpful but minimal.

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, consisting of a single sentence with no redundant information. It is front-loaded and quickly conveys the essential 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 absence of an output schema, the description does not hint at the return format (e.g., list of IDs, names, or full details). For a simple list operation with good annotations, it is minimally adequate but could be more complete by mentioning what information is returned.

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 for parameters is 100%, so the baseline is 3. The description does not add any additional parameter meaning beyond what the schema already provides. It does not explain how filters interact or the format of filter values.

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 'route tables' with scope 'in the current region'. It effectively conveys the tool's purpose. However, it does not explicitly differentiate from sibling tools like ncloud_get_route_table_detail, which could be used for a single route table.

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 no guidance on when to use this tool versus alternatives. There is no mention of use cases, exclusions, or how it relates to other route table tools like ncloud_create_route_table or ncloud_get_route_table_detail.

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