search_wireguard_peer_allowed_ips

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds 'filtering and pagination' as behavioral traits, but these are already reflected in the input schema parameters (page, page_size, peer_id, sort_by). Since the description repeats what the schema already communicates without adding deeper context (e.g., default sorting, result limits, or relationship to peer entities), it provides minimal additional behavioral disclosure beyond annotations.

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 that fully conveys the tool's purpose without unnecessary words or repetition. Every word earns its place, and the structure is highly compact and front-loaded.

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?

The tool is a straightforward read-only search operation with an output schema and full parameter documentation. The description combined with the structured data (annotations and input schema) provides all necessary information for an agent to select and invoke the tool correctly. No additional return-value explanation is needed because the output schema exists.

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 all four parameters, each with clear descriptions. The description's mention of 'filtering and pagination' summarizes the parameter behavior but does not add meaning beyond the schema. The schema itself provides all necessary parameter semantics, so the description adds no extra value here.

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 'Search WireGuard peer allowed IPs with filtering and pagination' uses a specific action verb ('Search') and clearly identifies the resource ('WireGuard peer allowed IPs'). It distinguishes itself from sibling tools like search_wireguard_peers, which targets the peers themselves, and manage_wireguard_peer_allowed_ip, which manages individual allowed IPs.

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 clearly establishes the tool's context as a search/filter operation for allowed IPs. While it does not explicitly mention alternatives or exclusions, the resource is unique enough that no ambiguity exists about when to use it versus other WireGuard tools. The readOnlyHint annotation reinforces that this is a safe read operation, but the description itself offers no additional guidance on when to choose it over similar search tools.

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