Get Sidebar Profiles

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavioral detail beyond that: it follows 'Show all' links to return the full list rather than a truncated preview, and it silently skips sections that redirect to linkedin.com/premium. That extra fan-out behavior is exactly the kind of context an agent needs, though it doesn't mention rate limits or failure modes.

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 what it returns and where it reads from, then the fan-out behavior, then the skip rule. No filler, no repetition of the title or schema.

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?

An output schema exists, so return payload shape need not be explained, and annotations carry the safety profile. The description covers source sections, expansion behavior, and skip logic, leaving only edge cases (e.g., empty sections, section ordering) unspecified — a minor gap.

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 there is only one parameter, so the schema already documents linkedin_username (including the URL-or-handle form and examples). The description adds nothing about the parameter, which is the expected baseline 3 when the schema does the work.

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+resource (get profile links) and narrows the scope precisely to sidebar recommendation sections on a profile page, enumerating the exact sections: 'More profiles for you', 'Explore premium profiles', 'People you may know'. This is enough for an agent to distinguish it from siblings like search_people or get_person_profile without inspecting their schemas.

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 tightly scoped resource (sidebar recommendations only), but the description never states when to prefer this over get_person_profile, search_people, or get_feed, and gives no prerequisites or exclusions beyond the premium-redirect skip. Adequate but leaves routing to inference.

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