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 usefully discloses the cost (3 credits) and the auth requirement (Bearer token), which is genuine behavioral context beyond structured fields, but it omits rate limits, error behavior, and pagination.

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 the core purpose and compact overall. Minor flaws: a double period after 'followers' and a boilerplate 'Platform=linkedin resource=profile' segment that mildly duplicates the tool name.

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 one-parameter tool with no output schema, the description covers the essential elements: what it fetches, the fields returned (compensating for the missing output schema), cost, and auth. It is adequate though it could note prerequisites or failure modes.

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?

With 100% schema description coverage and a single well-exampled 'url' parameter, the schema already documents the input. The description restates URL-based lookup but adds no syntax or format detail beyond the schema, so the baseline of 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) and resource (public LinkedIn person profile by URL), and enumerates the fields returned. It implicitly distinguishes from siblings like linkedin_company by scoping to a 'person' profile, though it never names the alternative explicitly.

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?

Usage is implied by 'person profile by URL' and the sibling set, but there is no explicit when-to-use/when-not guidance and no mention of linkedin_company or linkedin_post as alternatives for other LinkedIn resource types.

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