Get Person Profile

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile are covered. The description adds nothing on top: no mention of authentication requirements, scraping/rate-limit behavior, latency implications of scrolling, or that it fetches a live public profile. For an open-world read tool this is a missed opportunity.

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?

A single front-loaded sentence with no filler or repetition. It is efficiently sized, though arguably so terse that 'conciseness' shades into under-specification rather than tightness.

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 values need not be explained. But for a tool with three parameters, a pagination knob, and several near-neighbor tools, the description omits all routing context and any hint that heavy sections should be requested separately, leaving the agent to rediscover schema-only guidance.

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%, so sections and max_scrolls are thoroughly documented in the schema (including defaults, limits, and trade-off advice). The description adds no parameter meaning beyond that, which is the expected baseline of 3 when the schema carries the full load.

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?

States a clear verb ('Get') and resource ('a specific person's LinkedIn profile'), which is enough for an agent to know it retrieves a third party's profile rather than the caller's own. However, it never names the sibling it is distinguished from (get_my_profile) or clarifies the boundary with search_people, so differentiation is left to inference.

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 when-to-use guidance, no prerequisites, and no named alternative. With siblings like get_my_profile, get_company_profile, and search_people in the same family, some routing guidance would be cheap and valuable; the description supplies none.

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