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

With no annotations at all, the description carries the full burden, and it does disclose two real behavioral traits: keyless access and a concrete cost ($0.005, with an x402/Base payment route). It says nothing about failure modes, timeouts, rate limits, or what the returned payload looks like, so the disclosure 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?

Front-loaded with the core value proposition and kept to two compact clauses. The bracketed x402 endpoint/price fragment is jargon-dense but earns its place by telling the agent an alternate paid access path exists.

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 output schema and no annotations, the description is the sole source of information about the tool, and it covers inputs, signals, cost, and payment adequately on the surface. It stops short of describing the response shape, error behavior, or result freshness/latency for a 'live' probe, so an agent cannot fully anticipate the call's behavior.

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 coverage is 0% for the single required 'domain' parameter, so the description must compensate. It implies the domain is the subject being probed but gives no format guidance (bare hostname vs. URL, IDN/TLD handling), which is a mild but real gap for a one-parameter tool.

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 a specific resource and enumerates the exact signals produced (DNS MX/SPF/DMARC/A plus an HTTPS probe), so the agent knows precisely what it gets back. It does not, however, differentiate itself from the very similar sibling lion_domain_enrich, leaving ambiguity about which domain tool to pick.

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?

There is no statement of when to use this versus alternatives, no prerequisites, and no exclusions despite several overlapping siblings (lion_domain_enrich, lion_web_enrichment_bundle, lion_quick_intel). The agent must infer usage from the signal list alone.

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