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

With no annotations, the description carries the full burden and does disclose meaningful traits: it is an x402 paid GET endpoint, costs $0.03 on Base, and is positioned as a taster with a paid upsell. Missing are return-shape, latency, and any auth/rate-limit context, so it is helpful but incomplete for a payment-gated tool.

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 purpose is front-loaded, which is good, but the trailing bracket repeats the price already stated in the first line and packs curl-style endpoint syntax into prose. The '$0.03' duplication and mixed currency/endpoint notation make it denser than needed.

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 paid, no-annotation, no-output-schema tool, the description lists rough content categories but never states the response format or fields an agent should expect, and leaves the 'domain' parameter undocumented. It covers pricing and positioning but not enough for a caller to fully know what they receive.

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%: 'q' is documented as 'Company or domain' but the 'domain' parameter has no description anywhere. The '?q=coinbase.com' example clarifies that 'q' accepts a bare domain, but the description never explains the 'domain' parameter or the q-vs-domain relationship, leaving real ambiguity.

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?

States a specific verb+resource: 'KYB company dossier / company research pack' with three concrete components (web + firmographics + domain trust). It partially differentiates from siblings by naming the 'verified company file' it upsells and calling itself a 'taster'. However, it does not clearly distinguish itself from close siblings like lion_company_research or lion_company_enrich.

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?

Usage is only implied: 'Vendor intel taster; upsell verified company file $0.95' hints this is a cheap surface-level call versus the deeper paid file, and the '?q=coinbase.com' example shows intended input. There is no explicit when-to-use/when-not statement or named alternative among the many siblings.

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