create_ipsec_phase1

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

The annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds no behavioral context beyond the literal create action. It does not disclose the apply_immediately effect, config persistence, or whether the entry is active immediately.

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. It is appropriately front-loaded with the verb and object, making it instantly clear what the tool accomplishes.

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?

Despite full schema coverage, the description leaves out how Phase 1 relates to Phase 2 and whether creation immediately applies changes. For a complex IPsec configuration tool with 14 parameters, this minimal context is insufficient for an agent to understand the broader workflow.

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 14 parameters have descriptions in the schema (100% coverage), so the description contributes no additional parameter semantics. The schema already documents required fields, defaults, and conditions like pre_shared_key being required for pre_shared_key auth.

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 uses the specific verb 'Create' with the resource 'IPsec Phase 1 (IKE) entry', clearly distinguishing this from Phase 2, update, and delete sibling tools. It precisely states the tool's primary function.

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 usage guidance is provided. The description does not mention when to use this over update_ipsec_phase1, nor any prerequisites such as existing IPsec enablement or the need to create Phase 1 before Phase 2.

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