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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the $0.02 per-successful-call price, the x402/USDC-on-Base payment mechanism and the exact _meta key, plus billing rules (bad input free, not-found not charged) and the refusal behavior for personal profiles. That is exactly the cost/auth context an agent needs before spending money.

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?

A single dense paragraph that leads with the resource and scope, then pricing. The long field enumeration is useful for an agent with no output schema but is the one part that could be trimmed.

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?

Covers the input contract, the opt-in post feed with pagination, the field set that substitutes for a missing output schema, and the payment/auth and billing rules. Nothing essential to calling it correctly or safely is missing.

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%, so the schema already documents url, posts and cursor in comparable detail, and the description mostly restates them. The only added nuance is that posts triggers an extra vendor call and next_cursor pages the feed, which is already in the schema text, so the 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 and resource ('one LinkedIn company page by URL or page name') and enumerates the returned fields (industry, size, HQ, specialties, logo, recent posts). It also explicitly excludes personal profiles, which cleanly separates it from the sibling linkedin_profile tool.

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?

Gives a clear use case ('B2B research'), states the company-pages-only constraint, and explains when to add posts=1. It never names linkedin_profile as the alternative for personal profiles, leaving the agent to infer the routing, so it stops short of a 5.

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