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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the mutation/safety profile is covered. The description adds genuinely useful context: it operates only on the authenticated user's own profile (auth scope) and which fields the API silently does not support. It omits partial-update semantics, whether an existing experience entry is replaced or merged, and what happens when the tool is invoked given the 'not available' caveat.

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?

Four short sentences with no filler, front-loaded on the core capability before the exclusions. Minor weakness: the most consequential sentence ('Not available in this version') is buried last and reads as an afterthought rather than a headline caveat.

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?

For a nested-object mutation tool with no output schema, the description covers supported operations and the auth scope but leaves key operational questions unanswered: partial-update behavior, experience-entry merge/replace semantics, and what an agent should expect if it calls a tool declared unavailable. Adequate but with clear gaps.

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 the schema already documents location, experience sub-fields, and in_workspace in detail. The description's '(role, company, skills, dates)' merely restates a subset of the experience properties and adds no format or constraint detail beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 ('Update the authenticated user's own LinkedIn profile') and enumerates exactly what can be changed (experience entries, location) versus what cannot (headline, summary, education). That field-level scoping separates it from linkedin_raw_request. The trailing 'Not available in this version' blurs whether the tool actually performs any action, which keeps it short of a 5.

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?

It gives partial when-not guidance by ruling out headline, summary, and education, which steers the agent away from unsupported edits. However it never names an alternative (e.g. linkedin_raw_request) for those unsupported fields, and the 'not available in this version' clause is a confusing availability statement rather than a usable when-to-use rule.

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