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

With no helpful annotations, the description carries the behavioral burden. It discloses that saves persist across sessions and that each job can only be saved once. It stops short of specifying duplicate-save error behavior, but the key persistence and uniqueness traits are present.

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 action and is appropriately compact. Minor redundancy exists between 'agent memory across sessions' and 'saved jobs persist,' but no sentence is wasted.

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 simple mutation tool with a fully documented schema and no output schema, the description covers purpose, persistence, note usage, and the uniqueness constraint. The only notable omission is explicit behavior on duplicate saves, but the constraint itself is disclosed.

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 coverage is 100%, so the schema already documents all parameters. The description adds meaningful context by mapping jobType to AI-extracted jobs vs internal partner jobs and giving practical note examples, going beyond the bare enum labels.

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?

States a specific verb and resource: 'Save a job to the user's list for later.' It also differentiates the job types it supports and distinguishes itself from sibling save tools like save_education or save_project by naming the exact resource and purpose.

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 clear context on when to use it: when the user wants to keep track of interesting roles and across sessions. It does not explicitly name exclusions or alternatives like apply_to_job or unsave_job, but the intended use case is well conveyed.

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