typo_homoglyph

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

With no annotations provided, the description carries the full burden. It does disclose a key behavioral trait: 'Checks DNS registration for each variant,' implying a read-only network operation. However, it omits details such as output format, potential rate limits, or whether the tool returns resolved vs. available domains, so transparency is partial.

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, front-loaded sentence with no redundancy. It efficiently conveys the core purpose and a key secondary action (DNS check), 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?

The description covers the generation method and DNS registration check, which is sufficient to understand the tool's role among many siblings. However, it lacks explicit detail about return values (e.g., does it return a list of registered domains or available ones?) and variant scope, which would make it fully complete for an agent without an output schema.

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 fully documents the single 'domain' parameter with 100% coverage, including an example. The description adds no extra parameter semantics beyond the implied 'domain variants' reference, so it does not exceed the schema's baseline.

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 uses the specific verb 'Generate' and clearly identifies the resource ('domain variants') with explicit techniques (confusable characters, Cyrillic lookalikes) and the DNS registration check. This distinguishes it from sibling tools like typo_soundsquat or typo_combosquat by naming the specific homoglyph method.

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 guidance is provided for when to use this tool versus alternatives. The description is purely operational, stating what it does but not contrasting it with sibling homoglyph or typo tools (e.g., typo_idn_homograph, typo_keyboard_proximity). The agent must infer applicability from context.

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