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

With no annotations, the description carries the full burden of behavioral disclosure. It only reveals that results are limited to domains that currently resolve; it says nothing about how the search works, what data sources are used, response format, or any limitations. This is a significant gap for a tool with no structured safety hints.

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 brief and front-loads the core concept, with no wasted words. However, the leading 'Typosquat Finder' largely repeats the tool name, and the overall brevity comes at the cost of needed detail.

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?

Despite having an output schema, the tool lacks essential input context: what q means, what a valid query looks like, and how this tool differs from nearby siblings like homoglyph or punycode. An agent would struggle to invoke this tool correctly with only this description.

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 schema has one parameter, q, with 0% description coverage, and the description never mentions q or what value should be provided. The agent cannot infer whether q is a domain, keyword, or something else, so the description fails to compensate for the sparse 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?

The description says the tool finds look-alike domains that currently resolve, which gives a specific function and resource. It does not explicitly distinguish itself from related siblings like homoglyph or dns, but the 'currently resolve' qualifier adds useful specificity.

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 implies the tool is for typosquatting detection but gives no explicit guidance on when to choose it over alternatives such as homoglyph, whois, or dns. There is a clear context but no exclusion criteria or comparison to siblings.

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