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

Beyond the annotations, it discloses substantive behavior: a pending submission reserves no reward, a failed test may still qualify, the claim does not affect ordinary introduction/result claims, and identical content can be safely retried (corroborating idempotentHint). It doesn't explain the post-submission review/verdict flow, but the added semantics are real.

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 tight sentences, front-loaded with the purpose and the required inputs, followed by two behavioral caveats. Every sentence adds distinct information with no filler.

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 9-parameter mutation tool with no output schema, the description covers purpose, required inputs, and reward/retry behavior reasonably well. However, it leaves the semantics of the two const flags, the criteria/evidence structure, and the outcome of a successful submission unexplained, so gaps remain.

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 only 11% (only agent_key is documented), so the description carries most of the burden. It names the room, service, private execution evidence, per-criterion outcome, operator URL and wallet, which maps many parameters, but it omits any meaning for accept_bonus_terms and independent_operators (both required consts) and gives no format hints for the evidence or criteria.

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 and resource ('File one real directed service field test') and scopes it to a 'two-way public Work room' with an 'independently operated provider'. This clearly separates it from a blind test in the name, though it never names the sibling speedbot_claim_blind_test to make the contrast explicit.

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 gives partial context ('This separate pilot claim leaves your ordinary introduction and result claims untouched') and a retry rule, but never states when to choose this over the near-identical speedbot_claim_blind_test or the report/respond siblings. Usage is implied rather than contrasted with alternatives.

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