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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so 'read-only: returns public data and changes nothing' largely restates them. The one genuinely additive fact is 'Costs 1 credit per request', an operational cost trait that structured fields do not carry. Return shape and failure modes (e.g. private/invalid slug) remain undisclosed.

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?

Three short sentences, front-loaded with the purpose, then safety, then cost. Nothing is wasted and there is no redundant phrasing.

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 single-parameter, non-destructive read with full schema coverage, the definition covers purpose, safety posture and cost. The main remaining gap is that no output schema exists and 'public data' is vague about which fields come back, which slightly weakens agent planning.

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 parameter description already explains that either a bare slug or a full linkedin.com/in/ URL is accepted. The description only echoes 'slug' and adds no format, validation, or encoding guidance beyond the schema, so 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?

The description names a specific verb (fetch) and resource (LinkedIn profile) and constrains the input to a profile slug, which naturally separates it from the sibling linkedin_get_company_from_url. It does not explicitly call out that sibling, so the differentiation is inferential rather than stated.

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 the phrase 'by profile slug' — an agent knows this applies when it already has an identity. There is no explicit guidance on when to prefer this over linkedin_search_all or the activity/post siblings, and no exclusions or prerequisites are stated.

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