Get Sidebar Profiles

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

The description adds meaningful behavioral detail beyond the readOnlyHint and openWorldHint annotations: it follows 'Show all' links to get full lists and skips sections that redirect to linkedin.com/premium. This helps the agent understand what the tool will and will not return without inventing expectations.

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 description is compact and front-loaded with the core purpose, followed by two sentences of genuinely useful behavior details. Every sentence earns its place, with no filler or repetition of schema 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 single-parameter read-only tool with an output schema and safe annotations, the description is complete. It covers what sections are scraped, how 'Show all' behavior is handled, and which sections are skipped, so an agent has enough context to invoke it correctly.

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 description coverage is 100%, and the parameter linkedin_username is already well documented in the schema, including the accepted full-URL format. The description only restates that the parameter identifies the profile page to scrape, so it adds little semantic value beyond the schema.

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 states a specific action and resource: 'Get profile links from sidebar recommendation sections on a LinkedIn profile page.' It also names the concrete sections ('More profiles for you', 'Explore premium profiles', 'People you may know'), which clearly distinguishes it from broader sibling tools like get_person_profile or search_people.

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?

The description clearly implies when to use the tool: when sidebar recommendation profiles are needed from a LinkedIn profile page. However, it does not explicitly contrast this with alternatives or state when not to use it, so the agent is left to infer the boundary between this and other profile-related tools.

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