Add Work Experience

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

Annotations (readOnlyHint=false, destructiveHint=false) indicate a non-destructive write. The description adds behavioral context: no fabrication, require accurate dates, and the importance of avoiding duplicates (consistent with idempotentHint=false). No contradictions.

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?

Front-loaded with the core action, and structured into sections (description quality, technologies). Some redundancy (e.g., asking user to fill gaps mentioned twice) could be trimmed, but every sentence is informative. Slightly long but appropriate for complexity.

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?

Covers preprocessing (duplicate check), data quality (ask for missing info, date format), and content guidelines. Lacks output/response details (no output schema), but given the tool's nature, the description is mostly 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?

Schema has 100% description coverage, baseline 3. Description adds significant meaning: for 'description' provides quality and measurement guidelines; for 'technologies' instructs to always populate; for dates instructs to confirm approximations. Adds value beyond 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 clearly states it adds a work experience entry to the user's profile ('Add a work experience entry'). It distinguishes from sibling tools like get_work_experience by instructing to check for duplicates before creating.

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?

Provides detailed when-to-use and how-to-use guidance: check existing entries with get_work_experience to avoid duplicates, ask for missing or vague data, confirm dates, write professional descriptions with measurable outcomes, and always populate technologies.

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