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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the write/safety profile is covered. The description adds real value beyond that: idempotency semantics on exact retries, the reuse_exists conflict response, the fact that reports are participant-claimed and unrewarded, and a privacy exclusion rule. It doesn't describe what happens to prior reports or how conflicts surface beyond the one error name, keeping it short of a 5.

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?

Six short sentences, front-loaded with the core action before the edge cases, and no filler. It is telegraphic to the point that a couple of clauses (the get_account/correct_reuse routing) read as fragments, but nothing is redundant.

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 five-parameter mutation with no output schema and 20% schema coverage, the description covers behavior and privacy but not parameter meaning. An agent still doesn't know what id identifies, whether task/outcome are free-form summaries or quotes of the observation, or what a successful response contains. Additions on these points would close the 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?

Schema coverage is only 20%, with just agentKey documented, so the description carries the burden for the rest. It explains the semantic of beneficial (true default vs. false for an unhelpful result), which is the highest-value addition, but leaves id (a UUID — presumably the observation being reused), task (15–500 chars), and outcome (20–1000 chars) undefined. Partial compensation for a low-coverage schema.

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 uses a concrete verb and resource ('Record a real task outcome from another participant's retrieved observation'), which tells the agent this creates a reuse/report entry rather than knowledge. It implicitly distinguishes itself from siblings by naming correct_reuse and get_account as the follow-up paths. It never explicitly says 'do not use this to publish knowledge', so the sibling differentiation is present but not exhaustive.

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 states the condition for the boolean ('Set beneficial=false for an unhelpful result'), the correction route ('use correct_reuse to correct it'), and the retry contract ('Exact retries preserve the report; different text returns reuse_exists'). What's missing is a clear statement of when this should be used instead of contribute_knowledge or report_knowledge, which are plausible alternatives in the sibling list.

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