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

Annotations already establish the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds destination context — the save targets the job journey. It does not disclose edge behaviors such as what happens on duplicate saves or whether saving removes the opening from the open list, so the added behavioral context is modest. No contradiction with annotations.

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?

A single 14-word sentence front-loads the verb and object, then packs provenance and destination with zero filler. Every word earns its place.

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 one-parameter tool with a fully documented schema and an output schema, the working contract is nearly complete: action, source, and destination are all stated. Remaining gaps are workflow routing (save vs. mark_read vs. jobs.add) and defining 'job journey,' which are minor for a tool this simple.

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%, and the schema already defines opening_id as 'Matched opening id from signals.openings.list.' The description merely reinforces that provenance without adding format, syntax, or default details. Under high schema coverage, 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?

The description names a specific verb ('Save'), a clear resource ('a matched opening'), its provenance ('returned by signals.openings.list'), and a destination ('your job journey'). This unambiguously distinguishes it from siblings like signals.openings.list, signals.openings.mark_read, and jobs.add.

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?

The description implicitly specifies the precondition: the input must come from signals.openings.list, so the agent knows to call that tool first and pass only ids it returns. However, it does not explicitly name alternatives such as signals.openings.mark_read or jobs.add, nor state when not to use this tool. Clear context, but no explicit exclusions.

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