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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, and the description corroborates the destructive/monetary nature by disclosing the 1000-unit spend, the two-agent participation, and conditional payment on the locked test. It adds genuinely useful operational facts (concurrency limit, daily cap, replay-past-cap) but does not cover failure modes, whether funds are recoverable, latency, or what is returned normally versus as a replay. Note the mild tension between 'returns the last run as a replay' and idempotentHint=false, though that reflects cap behavior rather than true idempotency, so it is not a contradiction.

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?

Two sentences, front-loaded with the action and the funding source, followed by the constraint/edge-case sentence. No filler or restatement of the name.

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 burden of explaining outcomes, and it does describe the payment outcome and the cap-replay case. It does not describe the normal success payload (e.g., job identifier or status fields an agent would need to follow up via knos_near_job_status), which is the main remaining gap.

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 takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The embedded constants (bid of 1000 test units, two agents) are helpfully stated even though they are not schema fields.

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 compound action (fund one NEAR testnet job with a 1000-unit bid, have two agents take/submit it, and let the checker pay only the passing agent), which is far more informative than the title alone. It does not explicitly contrast itself with close siblings such as knos_near_job_status or knos_near_swarm_job, so an agent must infer the boundary from names.

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 establishes clear operating context: testnet only, test tokens only, capped at one run at a time and 20 per day, with replay behavior past the cap. It stops short of saying when to prefer this over a sibling job runner or status tool, so alternatives are left implicit.

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