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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool combines subdomain surface enumeration with email-pattern dork generation, but says nothing about data sources, read-only vs. mutation behavior, authentication, rate limits, or safety considerations. The output schema covers return values, but operational behavior remains opaque.

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 very short, but it reads as a cryptic label fragment rather than a structured, front-loaded sentence. Brevity here reflects under-specification, not efficient communication of the tool's purpose and usage.

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?

With no annotations, one undocumented parameter, and 0% schema description coverage, the description should compensate but does not. The output schema reduces the need to explain return values, but an agent still lacks enough context to confidently select and invoke this tool over its many siblings.

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 named 'q' with no description and 0% schema coverage. The description's phrase 'for a domain' weakly implies that 'q' expects a domain, but it does not confirm the mapping, specify a format, or explain optionality/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 names the resource area ('Domain Emails') and two activities ('Subdomain surface' and 'org email-pattern dorks'), so an agent can infer an OSINT email/domain enumeration purpose. However, it uses terse jargon without a clear verb and does not differentiate itself from siblings like email_crosssite, dorks, subdomains, or emailformat.

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 phrase 'for a domain' implies the input context, but there is no explicit guidance on when to use this tool versus alternatives such as emailformat, dorks, subdomains, or email_crosssite. No exclusions or prerequisite conditions are given.

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