create_ipsec_phase1_encryption

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the agent knows this is a mutating but non-destructive operation. The description adds no additional behavioral context, such as whether changes require applying via apply_ipsec_changes or whether duplicate entries are rejected.

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?

Description is a single clear sentence with no redundant information. It is front-loaded with the verb, but offers minimal detail beyond the name.

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?

For a tool with 7 parameters and an output schema, the description is extremely sparse. It fails to explain that parent_id must reference an existing Phase 1 entry, that some algorithms require key lengths, or that changes may need to be applied via apply_ipsec_changes. The output schema helps, but the description doesn't provide essential usage context.

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 provides 100% coverage with descriptions for all 7 parameters including allowed values for dhgroup, encryption_algorithm_name, etc. The tool description adds no extra parameter information, so baseline of 3 applies.

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?

Description uses specific verb 'Create' and resource 'IPsec Phase 1 encryption algorithm entry', clearly distinguishing from Phase 2 encryption creation. It states exactly what the tool does.

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 like search_ipsec_phase1_encryptions or create_ipsec_phase2_encryption. No exclusions or prerequisites mentioned.

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