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

Beyond the readOnly/destructive annotations, the description discloses the payment model (0.10 USDC per call on Base via x402 exact, plus 10 signed-wallet free calls per rolling 30 days), the auth scheme (X-Wever-Wallet-Proof bound to the exact JSON arguments and route, with Payment-Signature added on paid calls), and that the response carries an Ed25519 signed receipt. It also states the operational boundary — standing jobs run read-and-report tools only and never move money or change state — which is exactly the kind of behavioral context annotations cannot convey.

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 purpose is front-loaded, and most sentences carry real information, but the payload is delivered as one sprawling run-on enumeration that mixes return contents, pricing, auth headers, and doc links without paragraph or priority structure. The density is justified by the tool's complexity, yet the packaging makes key operational facts (cost, auth binding) hard to locate on a fast read.

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 carries the return-value burden itself and does so thoroughly, naming the report fields and the signed receipt. It also covers cost, free-tier limits, authentication requirements, link to the contract and human page, and the POST route — everything an agent needs to invoke it successfully.

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%, so the baseline is 3, but the description earns above it by adding the ownership constraint on job_id (the job must be owned by the calling wallet) and clarifying that run_index selects which run is returned in full versus defaulting to the latest. Both parameters gain meaning that the schema's terse field descriptions do not supply.

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 enumerates exactly what a caller gets back — schedule, run counts, last result summary, recent failures with error codes, next run, and one full signed run report — which makes the resource and scope unmistakable. The weakness is that no explicit verb leads the sentence and no sibling (e.g. wever_schedule-list, wever_watch-status) is named to sharpen the boundary, so distinction from related status/list tools is inferred rather than stated.

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 when-to-use guidance: nothing says whether to call this instead of wever_schedule-list for a summary or after wever_schedule-create, and no preconditions beyond the implicit requirement that the job belongs to the calling wallet. The only contextual aid is the note that past run records stay readable after the job ends, which is a fact about longevity rather than routing guidance.

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