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

The annotations already declare idempotentHint=true and destructiveHint=false, and the sentence 'Saving a job already saved changes nothing' largely restates that rather than adding new context. It does clarify caller-scoped ownership and that no side effect occurs on repeat calls, but says nothing about auth requirements or what the response contains.

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 short sentences, front-loaded with the action and scope, then idempotency, then the usage trigger. Nothing is wasted or buried.

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 single-parameter write with full annotation coverage and no output schema, the definition covers what is needed to call it. A brief note on what saving returns or where it appears (e.g., list_bookmarks) would close the last gap.

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 description coverage is 100% — the slug pattern and its origin ('list_matches or list_bookmarks') are fully documented in the schema. The description only echoes 'by slug', so baseline 3 applies with no extra value contributed.

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 caller's saved jobs, by slug') with the scoping that the job belongs to the caller. It is easy to distinguish from the sibling unsave_job and from read tools like get_job.

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?

'Use it when the user wants to keep a job for later' gives a clear use condition, and the slug source is implied by the schema. It stops short of naming unsave_job as the inverse or stating when not to use it.

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