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

With no annotations, the description carries the full burden, and it does add real operational facts: $0.04 cost, keyless access, apollo_org output format, and the x402 paid endpoint on Base. It omits whether the call is read-only, what happens on a miss, rate limits, and the response shape, so it is useful but incomplete.

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?

Dense and front-loaded with the core purpose first. Minor waste: the $0.04 price is stated twice (in prose and again in the x402 bracket), and the Apollo/x402 jargon adds noise without clarifying behavior.

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 an enrich tool with no annotations, no output schema, and zero schema coverage, the description supplies some pricing/payment context but leaves the return payload, identifier syntax, and field-selection mechanics unstated. Adequate but with real gaps an agent may need to fill.

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%, so the description must compensate for three undocumented parameters. It gestures at each: 'domain or name' for identifier, 'format=apollo_org' for format, and the field list for fields, but never matches these to the actual parameter names or gives value syntax.

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 (company enrichment) and enumerates the returned firmographics (name, employees, country, website), plus the accepted input key (domain or name). However, it does nothing to separate itself from overlapping siblings like lion_company_enrich, lion_domain_enrich, or lion_wikidata_firmographics, so it stops short of a 5.

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?

'Firmographics by domain or name' implies acceptable input, but there is no when-to-use guidance, no exclusion, and no pointer to the many adjacent enrichment tools an agent could pick instead. The agent is left to guess which enrichment sibling is appropriate.

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