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

Beyond readOnlyHint=true, description adds credit cost, details of returned fields (id, handle, canonical_url), error for non-LinkedIn URLs, and specific URN extraction logic. No contradictions with annotations.

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?

Description is well-structured with front-loaded purpose, but the output format details make it slightly verbose. Still reasonably concise and organized, earning a 4.

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?

Given output schema exists, description sufficiently explains return values, cost, error handling, and integration with sibling tools. No gaps for a resolve tool with clear annotations.

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% with clear description for the url parameter. Description adds extra context: supports utm params, subdomains, trailing slashes, and gives examples, exceeding schema baseline of 3.

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 clearly states it identifies what a LinkedIn URL points at, with specific verb 'resolve' and resource 'LinkedIn URL'. It distinguishes from siblings like linkedin_get_profile and linkedin_get_company by explaining when to use this tool first.

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?

Explicitly says when to use (before fetching a LinkedIn URL) and when not to use (when already have slug/URN/clean URL, as direct tools accept those). Names alternative tools and warns about credit cost, providing clear decision guidance.

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