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

With no annotations provided, the description carries the full burden. It discloses the operation is a read, includes a cost indicator ($0.09 via x402), and names the data sources. It does not cover failure modes or rate limits, but for a simple read enrichment, the key behavioral traits are covered.

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?

Two sentences with zero fluff. The cost and purpose are front-loaded, and the description is appropriately sized for the tool's complexity.

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 explains what data is fetched and the use case, but does not describe the output format or the x_payment parameter. With no output schema, the agent is left without guidance on what the response looks like or how to supply payment. This is a significant gap for a paid enrichment tool.

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 50%: the domain parameter is described in the schema, but x_payment is not. The description adds nothing about either parameter, failing to compensate for the missing schema documentation. An agent would be left guessing what x_payment requires.

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 clearly states it is a Company/Domain Enrichment Connector that fuses RDAP domain data, DNS email provider, and Wikipedia profile in one call. It names specific data sources and the target use case (sales, research, qualification), distinguishing it from generic enrichment tools like b2b_lead_enrichment.

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 identifies the intended users (sales, research, and qualification agents) and implies a one-call convenience. It does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to know when this tool fits.

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