Get Sidebar Profiles

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

The description discloses it follows 'Show all' links to return full lists and skips sections redirecting to linkedin.com/premium, adding behavioral context beyond the given readOnlyHint and openWorldHint annotations. No contradiction.

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 sentences, front-loaded with a clear summary, followed by relevant behavioral details. No redundant or unnecessary words.

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?

A single-parameter tool with an output schema and safety annotations. The description covers source sections, the expand behavior, and the skip rule, providing sufficient context for the tool's operation.

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%, with the single parameter linkedin_username fully documented including examples. The description adds no additional parameter semantics, 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 clearly states it retrieves profile links from specific sidebar recommendation sections on LinkedIn profile pages, naming three section types. This specific verb+resource combination distinguishes it from sibling tools like get_person_profile.

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?

No explicit when-to-use or alternative tool guidance is provided. Usage is implied by the description of the function, but it does not tell the agent when to choose this over get_person_profile or other siblings.

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