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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the mutation and safety profile is covered structurally. The description adds one genuinely non-structured trait — that the call is free — plus the effect of storing into the user's saved jobs. It omits auth requirements and the already-saved outcome, so it adds moderate value only.

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 short sentence with the action front-loaded and no padding; 'Free' is a compact addendum. Slightly under-specified rather than verbose.

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 trivial one-parameter mutation with full annotation coverage and no output schema, the description is close to sufficient. The remaining gap is the unidentified job_id and the absence of any note on duplicate saves, which the idempotent hint only partially covers.

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 0% for the single required parameter job_id, and the description never mentions how to obtain or format a job id (nor points to get_job/find_job_matches as sources). With low coverage the description must compensate and does not.

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 (saves) and resource (a job to the user's saved jobs) with the product context Litjob. It is clear what happens, but it does not differentiate from the sibling add_job, which an agent could reasonably confuse with this tool.

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?

There is no guidance on when to use this versus add_job, no prerequisites (e.g. job must exist, must be logged in), and no statement about what happens if the job is already saved. The only extra signal is 'Free', which is a cost note rather than usage routing.

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