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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is largely structured. The description still earns credit for disclosing what actually happens: future runs stop immediately, an in-flight run is discarded, and past run records survive via wever_schedule-status — genuine consequence detail beyond the annotations. It does not describe the shape of the returned report beyond calling it a signed receipt, which keeps it from the top of the scale.

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?

The core action and its effects are front-loaded in the first two sentences, before the endpoint, payment and contract boilerplate. The x402 pricing, wallet-proof and receipt block is dense but operationally necessary for an agent that must sign requests and pre-fund calls. It could be tightened slightly, but nothing is padding.

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?

No output schema exists, yet the description tells the agent what comes back (a report with an Ed25519 signed receipt) as well as the auth headers, request binding, and cost model required to call it successfully. For a one-parameter mutation tool, that is everything an agent needs to invoke it correctly.

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 coverage is 100% and the job_id pattern and description already cover the single parameter, so the baseline is 3. The description adds real meaning by stating the job must be owned by the calling wallet, which is a semantic constraint the schema does not encode. That is a modest but genuine increment over structured data.

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?

Opens with a specific verb and resource ("cancel a job") and pins the scope to "a job owned by the calling wallet." That ownership constraint plus the naming of wever_schedule-status makes it distinguishable from the sibling schedule-create/list/status tools without opening a 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?

The description gives a clear condition for use (cancel a job you own) and routes record-reading to wever_schedule-status, and clarifies the edge case that cancelling an already-ended job simply returns its final state. It stops short of an explicit "do not use this to pause or modify a job; use X instead" exclusion, so it is clear context rather than full when/when-not guidance.

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