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

The annotations are all false, so the description carries the behavioral burden. It adds important context: the stop is requested after the current job, nothing is left half-done, and already-sent applications remain sent. It could also disclose what happens if no run is active or whether the run can later be resumed, but the provided transparency is solid.

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 with no filler. The trigger phrases and core semantics are front-loaded, and the consequences are stated in a compact final sentence.

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 zero-parameter control action, the description covers purpose, scope, async behavior, and postconditions. It does not mention the no-active-run case or reversibility, but those are relatively minor gaps given the sibling tool get_apply_run_status could provide status context.

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?

The tool has zero parameters, so there is no parameter detail to clarify; the baseline for a zero-parameter tool is 4. The description correctly avoids introducing any phantom input options.

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: 'stop' an 'application run', plus the precise boundary ('after the job it is on'). Trigger phrases and the contrast with a running run make it easy for an agent to distinguish from start_apply_run and other sibling tools.

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?

Gives explicit trigger phrases ('stop applying', 'pause', 'hold off') and clearly implies it applies only to a running application run. It does not explicitly name alternatives or say when not to use it, but the intended use case is unambiguous.

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