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

No annotations are provided, so the description carries the full burden. It does disclose two genuinely useful traits the schema does not: a cost of 3 credits and a required Bearer api_key Authorization header, plus the fact that only public pages are fetched. It stops short of error behavior, rate limits, or what happens on invalid/private URLs.

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?

Purpose is front-loaded and the whole thing is short with no padding. A stray double period ('followers..') is a minor cosmetic flaw rather than a structural problem.

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 one-parameter public fetch with no output schema and no annotations, the description covers the return payload, cost, and auth, which is most of what an agent needs. Only edge-case behavior (invalid URL, private page) is unaddressed.

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% for the single url parameter, including an example, so the schema does the documentation work. The description only restates 'by URL' and adds no format or syntax nuance. Baseline 3 applies.

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 (fetch) plus the resource (public LinkedIn company page) and enumerates the returned data (about, size, industry, followers). The 'company' resource clearly separates it from siblings linkedin_job and linkedin_post without needing their schemas.

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 never says when to use this versus linkedin_job or linkedin_post, nor any precondition beyond the URL requirement. The 'Platform=linkedin resource=company' line is metadata, not usage guidance.

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