Normalize IP Address

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

Annotations provide readOnlyHint=true and idempotentHint=true. The description adds significant behavioral context: the tool operates locally with no API call or quota usage, and details the exact transformations applied (strip brackets, remove IPv4-mapped prefix, trim, lowercase). No contradiction 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?

The description is extremely concise with two sentences. The first sentence states the main action and details, the second adds usage context. No redundant 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?

Given low complexity (one parameter, no output schema), the description is complete. It explains the transformation, local execution, and zero cost. Sibling tools cover different operations, so no ambiguity.

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 the single parameter 'ip'. The description adds meaning by explaining what normalization does to the IP string, which complements the schema. However, it does not add further per-parameter semantics beyond the schema's description.

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 ('Normalize') and resource ('IP address string'), and lists clear actions (strip brackets, remove prefix, trim, lowercase). It distinguishes normalize_ip from sibling tools like geolocate_ip or validate_ip by focusing on transformation rather than lookup or validation.

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 explicitly says 'Runs locally — no API call, no quota usage', guiding the agent to use this tool when a quick, cost-free normalization is needed versus alternatives that may involve external calls. Exclusions are implied rather than stated.

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