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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value beyond that: the two-stage termination (polite request, then force after two seconds) and the no-op-on-finished-job behavior, which explains both destructiveness and idempotence concretely.

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?

One sentence plus a parenthetical, front-loaded with the action and the origin tool, with zero redundant phrasing. Every clause (escalation timing, finished-job no-op) 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 3-parameter mutation tool with no output schema, the description covers origin, escalation semantics, and the no-op case, while annotations cover destructiveness and idempotence. It omits return/failure reporting, but that gap is minor given the schema is self-documenting.

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 itself explains all three parameters (job id from job_start, host id from hosts_list, optional username). The description adds no parameter-level detail, so the baseline 3 applies — the schema carries this dimension entirely.

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 gives a specific verb (stop) plus resource (background job) and explicitly anchors it to the paired sibling job_start, distinguishing it from job_list/job_status. An agent can identify this as the termination counterpart to job_start without reading any schema.

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?

It states the originating context ('started with job_start') and the edge-case condition ('does nothing if the job already finished'), so the agent knows it is safe to call blindly on an unknown job state. It stops short of naming explicit alternatives or when-not-to-use guidance, but the pairing makes usage unambiguous.

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