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

With no annotations provided, the description carries the transparency burden. It usefully discloses that the operation costs 2 credits, that empty results and failures are never charged, and that cache=true returns a free 24h cache hit. However, 'Native 1 / enrich 2' is an unexplained, internal-sounding behavior that could confuse an agent, and it does not mention authentication, rate limits, or response shape.

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 description is short and front-loads the core purpose and key data fields before moving to compact operational notes. It earns most of its place, but the cryptic 'Native 1 / enrich 2' fragment is unexplained and slightly undermines the structure.

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 simple two-parameter read tool with no output schema, the description covers the main purpose, listed return fields, credit cost, failure billing, and cache behavior. The remaining gaps are the unexplained 'Native/enrich' distinction and the absence of explicit sibling routing, but an agent can likely invoke it correctly using the provided URL and cache parameters.

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 100%, and the input schema already contains strong descriptions for both url and cache. The description adds operational details about credits and caching, but it mostly restates or supplements the schema without adding new parameter-level meaning. Baseline 3 is appropriate.

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 identifies a specific resource (LinkedIn company page) and enumerates the data fields it exposes: specialties, similarPages, employeeCount, founded, slogan, cover. It is clear enough to distinguish from sibling tools like linkedin_company_posts or linkedin_profile, though it lacks an explicit verb like 'fetches' or 'returns'.

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 phrase 'Company page for B2B intel' implies when the tool should be used. However, the description never names alternatives or explicitly says when not to use it, such as 'for company posts use linkedin_company_posts' or 'for individual profiles use linkedin_profile'. This is implied guidance rather than explicit routing.

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