ncloud_add_route

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

Annotations declare destructiveHint=false, indicating the tool is not destructive. The description adds no further behavioral context, such as whether adding a duplicate route fails or whether it requires specific permissions. With annotations already present, the description contributes little transparency beyond the 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 a single sentence of 6 words, perfectly concise and front-loaded. Every word is meaningful, and there is no redundancy or unnecessary information.

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 tool has 6 parameters (5 required) and no output schema, yet the description only states the basic action. It lacks context about prerequisites (e.g., route table must exist), inter-parameter constraints (e.g., targetTypeCode must match targetNo type), or expected results. The description is insufficient for an agent to fully understand the tool's behavior.

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?

The input schema has 100% description coverage, with each parameter documented (e.g., destinationCidrBlock pattern). The description does not add meaning beyond what the schema already provides. Baseline 3 is appropriate since the description adds no extra semantic value.

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 'Add a route to a route table' clearly specifies the action (add) and the resource (route to a route table). It distinguishes the tool from siblings like ncloud_remove_route and ncloud_get_routes, making it easy for an AI agent to select the correct tool for creating a new route.

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. It does not mention prerequisites, such as the need for an existing route table, or contrast with ncloud_remove_route or ncloud_get_routes. The agent is left to infer usage from the name alone.

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