networking_ipv4_to_ipv6

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

Description adds behavioral details beyond annotations: read-only, non-destructive, no external service contacts, rate limits (60 req/min, 500/hr). Also enumerates output types and classification. No contradictions with 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?

Single well-structured paragraph with each sentence adding value: purpose, method, output types, sibling differentiation, input format, behavioral notes. No wasted words.

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 output schema exists, description does not need to detail return values but still lists them. Covers all necessary context for a two-parameter tool with high schema coverage.

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 coverage is 100% with descriptions. Description adds that ipv4 must be dotted-decimal without CIDR suffix, and that input is a deprecated alias. This adds context beyond schema.

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 starts with 'IPv4 to IPv6 Converter' and clearly states it converts a single IPv4 address to IPv6 representations using offline arithmetic, distinguishing it from sibling tools for subnet planning and CIDR notation.

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?

Explicitly instructs to use network_subnet_calculator or network_cidr_calculator for subnet planning, and clarifies this tool only transforms one host address without CIDR parsing. States input format explicitly.

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