socials_linkedin_profile

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

No annotations are provided, so the description carries the full burden. It discloses 'auto-navigates' as a behavioral trait, implying a side effect on the current tab, and lists extracted fields. However, it does not mention authentication requirements, error handling, or potential impact on the browser session, which are relevant for an automated agent.

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 a single, well-structured sentence that front-loads the core purpose and immediately follows with the required input and expected output. No redundant words or filler; every word earns its place.

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?

The tool is simple with one parameter and no output schema. The description adequately covers the return values by listing the extracted fields. It lacks a note on whether navigation changes the current tab or opens a new one, and error behavior, but given the low complexity, the description is mostly complete.

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 a clear description and example for profile_url. The description merely repeats 'Pass profile_url' without adding meaning beyond the schema. The schema already provides the necessary parameter details, so the description adds no extra semantic value.

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 the tool's function: 'Get a LinkedIn profile' with a specific verb and resource. It lists the exact data fields extracted (name, headline, about, experience, education, skills, contact info) and distinguishes it from sibling tools like socials_x_profile (Twitter) and socials_linkedin_people_search (search).

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 gives clear usage context: pass profile_url to retrieve profile details. It does not explicitly name alternatives or exclusion cases, but the tool's specificity makes the intended use unambiguous. Sibling tools are distinct enough that no further guidance is necessary.

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