ipv6_expand

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

With no annotations, the description must convey behavioral traits. It describes the core transformation but does not specify error handling for invalid inputs or edge cases (e.g., malformed addresses). For a simple read-only tool, this is minimally adequate but lacks depth.

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 extremely concise: two sentences with no redundancy. The first sentence states the purpose, and the second lists the parameter. Every word serves a purpose, making it easy to parse quickly.

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 that an output schema exists (though not shown), the description does not need to explain return values. For a tool with one simple parameter and no annotations, the description covers the essential use case adequately. It could optionally mention that the result is the expanded address, but the output schema likely handles that.

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?

The input schema has 0% description coverage, so the parameter 'ipv6' is just a string type. The description adds meaning by labeling it as an IPv6 address to expand and providing examples ('::1', '2001:db8::1'), which helps the agent understand the expected format.

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 clearly states the tool's purpose: expanding abbreviated IPv6 addresses to full notation. The verb 'Expand' and the resource 'abbreviated IPv6 addresses' are specific and unambiguous. None of the sibling tools target IPv6 expansion, so it is well-distinguished.

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 provides no guidance on when to use this tool versus others. It does not mention prerequisites, acceptable input formats, or when not to use it (e.g., already expanded addresses). Given the many sibling tools, explicit context would help.

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