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 implies a read-style lookup and hints at output categories (registration, reputation, risk), but says nothing about data sources, whether the target is a domain or a legal entity, latency, cost, or result shape. Substantial disclosure is missing.

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 single sentence is short and front-loaded, but it opens by duplicating the name/title ('Company Check: Company check —'), spending its few words on redundancy rather than on the details the agent needs.

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?

For a tool with no annotations, no output schema, and two completely undocumented parameters, the description should explain what to supply and roughly what comes back. It mentions output categories but not inputs, so the definition is not complete enough to invoke confidently.

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 0% for two parameters ('input' and 'domain'), and the description never mentions either. Critically, it does not say whether the caller should pass a company name via 'input' or a domain, or whether both are expected — a genuine ambiguity that could cause a failed call.

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 ('company') and the kind of output it produces (registration, reputation, risk), which is more than a bare tautology. However, 'Company Check: Company check —' largely restates the title, and it does not distinguish this tool from close siblings such as x402-domain-intel, x402-domain-report, x402-domain-due-diligence, or x402-wallet-intel. The agent cannot tell why it should call this instead of those.

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 tool, when not to, or what the alternative is. With dozens of overlapping company/domain intelligence siblings listed, the absence of any routing guidance is a real gap.

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