calculate_ipv6_subnet

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

The description only says 'Calculate IPv6 subnet information', which implies a read-only operation. However, the annotation readOnlyHint is false, suggesting possible side effects. The description does not disclose whether the tool modifies any state or requires special permissions, creating a contradiction and insufficient transparency.

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, concise sentence that front-loads the key action and resource. However, it lacks additional context that could fit in the same space, so it scores well but not perfectly.

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 description is too brief given the lack of output schema. It does not explain what information the tool returns (e.g., network address, broadcast address, number of subnets), which is crucial for agent decision-making. Additional context about output format or typical use cases is missing.

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?

Both parameters are fully described in the input schema (100% coverage), so the baseline is 3. The description adds no additional semantic meaning beyond what the schema provides; it does not explain how the parameters interact or provide default behavior.

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 calculates IPv6 subnet information, distinguishing it from sibling tools for IPv4 (calculate_ipv4_subnet) and generic IP (calculate_ip_subnet). The verb 'calculate' and specific resource 'IPv6 subnet' provide clear purpose, though more detail on the exact output (e.g., network address, prefix) would be helpful.

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 usage guidelines are provided. The description does not indicate when to use this tool over its siblings (e.g., calculate_ip_subnet, calculate_ipv4_subnet), nor does it mention prerequisites or typical scenarios. This leaves the agent without decision support for tool selection.

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