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

Annotations only carry boolean flags, so the description carries the behavioral burden. It explains partial-update semantics ('changing only the fields you send'), the upsert contract, and adds guardrails against duplicates and fabrication. It stops short of disclosing auth needs or error behavior, so not a full 5.

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 the core upsert behavior and every sentence contributes value. It is slightly dense because it packs in content-quality and workflow guidance alongside tool mechanics, but it remains organized and efficient.

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 10-parameter upsert with no output schema, the description covers the full workflow: create/update choice, required fields, id sourcing, duplicate avoidance, and field-level content expectations. Missing return-value and error-case details are minor for tool selection and invocation.

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?

Even with 100% schema coverage, the description adds real meaning: title and startDate are conditionally required for create, ids come from get_profile, technologies feed job matching, and the description field has explicit WHAT/HOW/IMPACT/SCOPE content rules. This goes well beyond the raw schema.

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 'Add or update a work experience entry (upsert)', giving a specific verb, resource, and operation mode. This clearly distinguishes it from sibling save_education and save_project tools by naming 'work experience' as the target.

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 provides concrete create-vs-update logic: omit id to create, pass an id from get_profile to update, and check get_profile first to avoid duplicates. It does not explicitly name alternatives or state when not to use the tool, but the workflow guidance is clear and actionable.

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