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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, idempotentHint=false, so the safety profile is already covered. The description adds real behavioral context the annotations don't: persistence across sessions and the 'each job can only be saved once' constraint. It does not say what happens on a duplicate save (error vs. no-op), which is the one remaining ambiguity.

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 scope in the first sentence, followed by source tools, the memory rationale, the note example, and the once-only constraint. The memory/persistence sentences overlap somewhat in meaning, but overall it is 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?

There is no output schema, so the agent must infer the result of a save; the description doesn't state whether a successful save returns the saved record or how duplicates are reported. Given the mutation nature and the 'only once' constraint, the duplicate-call behavior is the notable gap. Otherwise it covers inputs, sources, and purpose adequately.

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 all three parameters (jobId, note, jobType) are already fully documented in the schema, including the enum values and the 24-hex pattern. The description corroborates the note's purpose with examples and ties jobType's ai_job value to search_jobs/get_starred_jobs, but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 (save), resource (job), and destination (user's list for later), which clearly separates it from unsave_job and get_saved_jobs in the sibling set. It also names the upstream tools that produce savable jobs (search_jobs, get_starred_jobs).

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?

Explains the use case well: persisting jobs across sessions and tracking interesting roles, and names the source tools that feed it. It does not explicitly state when NOT to use it or point to unsave_job/update_saved_job_note as follow-ups, so it stops short of full routing guidance.

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