Get Person Profile

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety and external-data nature are already known; the description adds no contradiction. The description itself does not reveal behavioral details like scraping behavior or result shape, but the rich parameter descriptions cover pagination and sections, so this is adequate.

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 sentence with no filler words. It front-loads the core purpose and does not repeat information already in the schema or annotations.

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 and the schema plus output schema provide substantial detail about sections, pagination, and return values. The description could be slightly richer by mentioning that the main profile page is always included, but this is already in the sections parameter description, so nothing critical is missing.

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 detailed descriptions for all three parameters: linkedin_username includes examples and URL normalization, sections lists all options and defaults, and max_scrolls explains its behavior and defaults. The main description adds no parameter-level meaning, but the baseline of 3 applies because the schema already does the heavy lifting.

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 verb ('Get') and resource ('a specific person's LinkedIn profile'), making the operation unambiguous. It clearly distinguishes this tool from siblings like get_my_profile (own profile) and get_company_profile (company profile) without needing to read the schema.

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?

There is no guidance on when to use this tool versus alternatives such as search_people, get_sidebar_profiles, or connect_with_person. The description only states what the tool does, not the conditions that make it the right choice, leaving selection to inference.

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