vpn_ipsec_phase2_list

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

With no annotations, the description must carry the burden of behavioral disclosure. It only states 'List all' without noting pagination, authorization needs, or output volume. No contradictions with annotations (none present).

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 unnecessary words. It is appropriately sized and front-loaded, earning its space.

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 simple nature (1 parameter, output schema present), the description is mostly adequate. However, it could mention the relationship to Phase 1 or that it returns all Phase 2 configurations per VDOM, adding slight 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 description coverage is 100% for the single parameter 'vdom', with a clear description. The tool description adds no additional semantics beyond what the schema provides, so it meets baseline.

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 states the verb 'List', the resource 'IPsec VPN Phase 2 (SA / child SA) selectors', and the scope 'all', making it clear what the tool does. This distinguishes it from sibling tools like vpn_ipsec_phase2_get (single) and vpn_ipsec_phase2_create (create).

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 explicit guidance on when to use this tool vs alternatives (e.g., vpn_ipsec_phase1_list, vpn_ipsec_phase2_get). It is implied that this is for listing all Phase 2 selectors, but the description lacks context about prerequisites or filtering.

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