deploy_create_network_tunnel_group

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

No annotations are provided, so the description carries the full burden. It only states 'Create' without disclosing any behavioral traits such as side effects, authentication needs, or limitations. The schema's passphrase description includes security notes, but the tool description does not.

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?

Two sentences, front-loaded with the primary action. No unnecessary words, every sentence earns its place.

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 creates a resource with 4 parameters and no output schema, the description lacks context about what a network tunnel group is, return value, prerequisites, or why/when to use it. Only a region hint is provided.

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?

All 4 parameters are described in the schema (100% coverage), so baseline is 3. The description adds a hint about using deploy_list_regions for region, but this is already in the schema. No additional meaning beyond schema for other parameters.

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 'Create a Network Tunnel Group,' which is a specific verb and resource. It distinguishes from sibling tools like deploy_list_network_tunnel_groups or deploy_delete_network_tunnel_group by the action.

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 a hint to use deploy_list_regions for the region name, but does not explain when to use this tool over alternatives or any prerequisites. No when-to-use or when-not-to guidance.

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