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

Annotations already cover the read-only/open-world safety profile, but the description adds genuinely new behavioral context: a concrete cost of 60 prepaid credits per successful call, a 'public data only' scope limit, and that the MCP layer returns only a compact view of results. Missing only failure/rate-limit behavior to reach 5.

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-loads purpose, then return shape, scope, price, and MCP formatting in tight succession with no filler. Dense but every clause carries information; slightly long in a single sentence but not wasteful.

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?

With no output schema, the description compensates by enumerating returned fields (name, headline, location, public identifier, biography). Input, output, cost, and data-scope constraints are all covered, leaving nothing essential for a correct call.

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 single profile_id parameter is already documented as the identifier from the profile URL. The description adds only a slight clarification that a slug is acceptable, so the schema does most of the work and 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 ('retrieve a person by profile ID or slug') plus the domain ('LinkedIn public profile API'), which cleanly separates it from the sibling search_* tools. An agent knows exactly what this returns without opening the 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?

Gives clear intended context: 'for lead research and profile enrichment', which tells the agent when this tool is appropriate. It does not name alternatives or state when not to use it (e.g., use search_web for discovery), so it falls 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.