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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is fully covered structurally. The description adds the ordering trait ('newest first') and the returned fields, but says nothing about how many jobs 'recent' covers or any pagination limit.

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 efficient sentence front-loaded with the verb and resource, with the field list in a parenthetical rather than burying it. No filler, though the field enumeration is arguably schema-level detail.

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?

With no output schema, the description compensates by naming the returned fields and their order, which is genuinely helpful. The remaining gap is the unbounded term 'recent', which gives no sense of result-set size or truncation behavior.

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%, so both parameters (host, username) including the default-user behavior are already documented in the schema. The description only confirms the server scope, adding no syntax or format meaning beyond that; 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 states a specific verb and resource ('List the recent background jobs on a server') and even enumerates the fields returned (id, state, start time, command). It does not, however, distinguish itself from the sibling job_status, which an agent might reasonably confuse it with.

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 explicit when-to-use guidance and no mention of the alternative job_status or job_start/job_stop, which operate on the same domain. The only usage signal is the implicit scope phrase 'on a server', leaving routing between job_* tools to inference.

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