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

With no annotations present, the description carries the full burden and does disclose a meaningful amount of behavior: it is keyless (no auth), costs $0.04, is billed through an x402 paid route on Base, and sources data from Wikidata+SEC. Missing are rate limits, failure behavior, and whether the identifier must be a domain, name, or LEI, which keeps it from a 5.

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 definition is a single front-loaded line that leads with purpose, which is good. It is nonetheless crowded with pricing, upsell, HTTP alias paths and x402 boilerplate that compete with the actionable content, so it reads more like a marketing blurb than a tight tool spec.

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, no annotations, and only three parameters, the description should do more than it does: it lists a few returned fields but never describes the response shape, and it omits the accepted identifier format. It is adequate to know roughly what the tool returns, but not complete enough to call it 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 coverage is 67%: 'fields' and 'format' are described in the schema, while the required 'identifier' parameter has no description anywhere. The description restates format=apollo_org and lists returned field names that loosely map to the 'fields' parameter, adding marginal value, but it leaves the most important parameter (what kind of identifier is accepted) entirely unexplained.

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 does state a resource (company/org enrichment) and the fields returned (name, employees, country, industry, website), and it names the data sources (Wikidata+SEC). However, it never distinguishes this tool from the closely overlapping siblings lion_company_enrich, lion_org_enrich, lion_wikidata_firmographics and lion_company_dossier, and the '/company-enrich /org-enrich' aliases actually muddy the picture rather than clarifying which 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 explicit when-to-use, when-not-to-use, or alternative-routing guidance. The only hint is the upsell line pointing at a richer verified company file at $0.95, which implies a tiering but never says when the $0.04 pack is insufficient or when to prefer lion_company_enrich / lion_org_enrich instead.

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