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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that no login is needed, that each result costs 1 credit, and that failed items are free — the kind of cost/auth context annotations cannot carry. It stops short of describing output shape, rate limits, or partial-failure behavior, which keeps it off 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?

Front-loaded with purpose and inputs, then the cost sentence; no filler. The middle field enumeration is long but each item is a concrete returnable attribute, so it earns most of its length.

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 read-only scrape with full schema documentation and no output schema, the description covers inputs, cost model and the data returned. Only secondary gaps remain: return structure/pagination and behavior on unresolvable domains.

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 100%, so the domains, maxResults and includePosts semantics are already documented in structured fields, and the description only gestures at them via the field list. Baseline 3 applies since the description adds no format or edge-case detail beyond the schema.

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?

Specific verb ('Get') plus a precisely scoped resource ('public LinkedIn company data') with inputs named (company URL or website domain). The enumerated field list (industry, size, headquarters, followers, similar companies, posts) makes it unmistakably distinct from the sibling linkedin-jobs.

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 implies when this applies by defining the two accepted input forms, and the schema adds the domain-to-LinkedIn-page matching rule. But there is no explicit routing guidance — nothing says when to prefer this over other enrichment/scrape siblings or when it will fail (private pages, ambiguous domains).

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