ncloud_add_acg_outbound_rule

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

Description provides minimal behavioral context. Annotations indicate destructiveHint=false, and description states 'Add', which is a mutation but not destructive. No mention of whether rules are appended or overwritten, or what happens on duplicate rule.

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?

Single sentence, no wasted words. Could be improved by including key constraints or usage hints, but remains appropriately concise for a simple action.

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?

No output schema and description does not mention return values or side effects. For a modification tool, the description lacks completeness about what the user can expect upon success or failure.

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%, so the schema already documents each parameter. The tool description adds no extra parameter information beyond what is in the schema. Baseline score of 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 'Add an outbound rule to an Access Control Group' clearly states the action (add) and resource (outbound rule to ACG). It distinguishes from inbound rule tools by specifying 'outbound', but does not explicitly differentiate from sibling tools like ncloud_remove_acg_outbound_rule.

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 on when to use this tool versus alternatives. Lacks context such as prerequisites (e.g., ACG must exist), or when to add vs remove rules. Does not mention that ipBlock and accessControlGroupSequence are mutually exclusive, though that is in schema.

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