experience

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses that experiences are managed on the LinkedIn profile, and notes position_id is required for update, but does not detail side effects of add/update/delete, authentication requirements, or the meaning of is_current beyond a parameter name. The allowed_args_for_action is a constraint map, not a behavioral explanation.

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 well-structured: a one-sentence summary, a clear list of parameters with examples, and an allowed-args map. Given the complexity of 12 parameters and three actions, the length is appropriate and each component adds value, avoiding wasteful prose.

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?

With an output schema present, the description adequately covers the input semantics for all parameters and action combinations. It is missing some operational context such as how delete matches entries using title/company, or what happens if multiple entries share the same title, but overall it is fairly complete for a complex tool.

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?

The schema has zero descriptions, so the description fully compensates by explaining every parameter with examples and clarifying the special role of position_id. The allowed_args_for_action map adds explicit per-action parameter constraints, going well beyond the schema's type/default definitions.

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 identifies the tool as managing experience entries on LinkedIn, which distinguishes it from sibling tools like education, job, and profile. The action enum and allowed args specify add/update/delete, adding clarity. However, the verb 'Manage' is generic, and the description does not explicitly contrast with related tools.

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?

Usage is implied by the resource name and the action parameter, indicating when to add, update, or delete experience entries. However, there is no explicit when-to-use vs alternatives guidance, no exclusions, and no mention of tool selection relative to siblings like education or job.

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