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

With no annotations, the description carries the full behavioral burden, and it does disclose genuinely useful non-obvious traits: no API key required, CC0 licensing, and a paid x402 route with an explicit price ($0.005) and network (Base). It says nothing, however, about return format, rate limits, or failure modes, 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?

A single sentence that front-loads the resource and tucks the payment metadata into a bracketed suffix. Almost no waste, though the bracketed endpoint/price string is dense and slightly obscures the core purpose.

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?

There is no output schema and no annotations, and the description does not explain the three unlabeled parameters or what firmographic fields are returned. For a tool with three undocumented inputs and no structured safety or return information, this is well short of complete.

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% and the description never mentions the q, qid, or entity parameters, their formats, or whether they are alternatives. Three fully undocumented parameters with no compensating text in the description leave the agent guessing how to call it.

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 (Wikidata firmographics) and adds distinctive qualifiers (keyless, CC0, paid x402 endpoint), so an agent knows it is a firmographic lookup backed by Wikidata. However there is no verb and no differentiation from the many overlapping company-enrichment siblings (lion_company_enrich, lion_org_enrich, lion_company_dossier), leaving the purpose only partially pinned down.

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 versus the numerous sibling enrichment/dossier tools, no prerequisites, and no hint about which of the three params to supply. The only routing signal is the implicit 'keyless/CC0' framing, which an agent must interpret on its own.

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