add_experience

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

With no annotations, the description carries the behavioral burden. It states that this is an 'Add' mutation and adds a valuable security scope ('Strictly locked to your authenticated account (/in/me)'). However, it does not disclose side effects such as public visibility, duplicate handling, validation failures, or any irreversible consequences, so behavioral detail remains only 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 front-loaded with purpose and security context, then presents a clean Args list. Each line earns its place and none of the prose is redundant or filler.

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 an 11-parameter tool with no annotations, the description covers all parameters, the target profile, and the authentication boundary. An output schema is present, so not describing return values is acceptable, and nothing needed to invoke the tool correctly appears to be 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 0%, but the description compensates fully: every parameter is explained with examples or allowed values. It even adds conditional semantics (end_month/end_year only if not current), a default for is_current, and enumerated choices for employment_type and location_type.

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 opens with a specific verb and object ('Add a work position or experience') and clearly scopes it to the user's own LinkedIn profile. This differentiates it from sibling tools like add_education, add_skill, and add_project without requiring an agent to inspect 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?

It establishes the correct context: adding a work-position entry to the authenticated user's own profile, and the security notice reinforces that it cannot act on anyone else's profile. It does not explicitly name alternative tools or say when not to use this one, so it falls just short of full routing guidance.

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