ipv6_normalize

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 discloses the three concrete outputs (expanded form, compressed form, address type) and scopes the operation to IPv6 normalization. It does not describe invalid-input handling or exact return structure, but for a pure formatting tool the core behavior is adequately transparent.

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 whole description is one focused sentence with no filler. The primary output is front-loaded, and every phrase carries meaningful information.

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 one-parameter, read-only formatting tool with no output schema, the description is largely complete: it enumerates the expected outputs and clarifies the input type. It could additionally describe error behavior or output layout, but that is a minor gap rather than a blocking omission.

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?

There is a single required parameter 'address' with no schema description coverage, and the description adds the key semantic that it must be an IPv6 address. However, it does not specify allowed input formats (e.g., brackets, uppercase, IPv4-mapped), nor what happens for invalid addresses, so the compensation is partial.

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 a specific verb ('Show') and a specific resource ('fully expanded form and correct RFC 5952 compressed form of an IPv6 address'), plus a third output category (address type). This clearly distinguishes it from siblings like ip_convert or subnet_calc by focusing specifically on IPv6 normalization and classification.

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 makes the usage context clear: use this tool when you need expanded or RFC 5952-compressed forms of an IPv6 address and its classification. It does not explicitly name alternatives or state when not to use it, so it does not reach the explicit-when-not/alternatives level.

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