create_nat_outbound_mapping

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

With annotations already indicating readOnlyHint=false and destructiveHint=false, the description adds no behavioral transparency beyond what is stated. It does not disclose whether the mapping takes effect immediately, how conflicts are handled, or any required permissions, despite the schema containing an apply_immediately parameter.

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 with no superfluous words, making it concise and front-loaded. While it is terse for a tool with many parameters, the schema compensates, and there is no bloat to penalize.

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 tool's complexity (13 parameters) and the presence of an output schema, the description provides only minimal context. It identifies the creation action but omits typical use cases, prerequisites, or operational notes, though the schema and annotations partially cover the gap.

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 provides thorough descriptions for all 13 parameters (100% coverage), so the description is not required to explain parameters. The description itself adds no additional meaning beyond the schema, matching the baseline for full schema coverage.

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 'Create an outbound NAT mapping' clearly identifies the action (create) and the specific resource (outbound NAT mapping). This distinguishes it from sibling tools like create_nat_port_forward and create_nat_onetoone_mapping by the explicit 'outbound' qualifier.

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 offers no guidance on when to use this tool versus related tools such as create_nat_port_forward or create_nat_onetoone_mapping. There are no mentions of prerequisites, alternatives, or exclusions, leaving the agent 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.