Update Work Experience

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

The description adds behavioral detail beyond annotations: partial update semantics ('omitted fields are left as-is'). Annotations already indicate idempotency and non-destructiveness, so the description complements them without contradiction.

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?

Three sentences with no redundancy: first sentence states purpose, second explains partial update, third gives usage guidance and alternative. Each sentence earns its place.

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 description covers prerequisites, partial update behavior, and alternative preference. Lacks mention of return value or error conditions, but for a straightforward update tool with high schema coverage and clear annotations, this is nearly complete.

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 input schema has 100% description coverage for all 10 parameters. The description only adds general partial update behavior, not per-parameter details. Thus, it meets baseline expectations but adds limited extra value.

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 states 'Update an existing work experience entry' with explicit partial update behavior. It distinguishes from siblings by mentioning 'prefer this over delete + recreate' and provides a prerequisite step (get_work_experience).

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?

The description explicitly says 'Use get_work_experience first to find the ID' and 'Prefer this over delete + recreate — it preserves the entry ID,' offering clear when-to-use and why, as well as an alternative approach.

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