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

Annotations already cover read-only and non-destructive, but the description adds substantive behavior: results are limited to what an incognito/logged-out visitor sees, work history and job titles are withheld, and repeated requests may re-purchase the same data. That last point is valuable for cost-aware agents. It is marred by a self-contradiction between 'at least 10 Nexscope credits' and '1 credit per request'.

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 first two sentences are front-loaded and dense with useful facts, but the text then devolves into pasted vendor marketing copy ('View Pricing', 'Examples are not guaranteed prices') and a contradictory per-request price. Those fragments cost attention without adding reliable information.

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 lookup with no output schema, the description covers what data comes back, what is withheld, and the cost implications. What's missing is failure behavior for private, deleted, or malformed profile URLs, plus a coherent single statement of the price.

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?

Only one parameter and schema description coverage is 100%, so the schema already explains 'url'. The description adds no format guidance (e.g. full linkedin.com/in/... URL vs handle), so it does not compensate beyond the baseline.

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 ('Retrieves a person's public LinkedIn profile data') and enumerates the returned sections (followers, about, posts, experience, education, articles, recommendations). The word 'person's' implicitly separates it from the sibling social_linkedin_company, so an agent can pick the right tool without opening either schema.

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: you need a profile URL and you get public data. There is a useful exclusion ('Work history and job title are not publicly returned'), but no explicit when-to-use vs sibling guidance, e.g. nothing telling the agent to use social_linkedin_company for company pages or social_linkedin_post for a single post.

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