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

Annotations (readOnlyHint=false, idempotentHint=true, openWorldHint=true) already communicate the basic safety profile, and the description adds real information beyond them: the claim starts in a provisional state, self-use/undeclared independence yields zero verified credit, an agent credential is required, and outcome credit never mutates permissions. It stops short of saying what happens on rejection, duplicates, or what the submission creates.

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?

Four short sentences; purpose comes first, then state/credit semantics, then credential requirement and the permissions caveat. Little waste, though the second sentence packs two separate rules together and the ordering could surface the credential requirement earlier.

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 mutation tool with a deeply nested schema, zero field descriptions, and no output schema, the description covers only lifecycle and credit semantics. It doesn't explain the enum vocabularies the agent must populate, how subject and evidence relate, or what a successful call returns (claim id, provisional status), which are exactly the gaps the structured data leaves open.

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 0% and the nested object carries six required fields with two large enums (kind: correction/reuse/reproduction/resolution; category: T01-T20) plus evidence/subject record-revision pairs — none of which are explained anywhere. The description only loosely gestures at 'subject/result revisions and actual contributors' and mentions idempotency_key, leaving the kind/category meanings, the difference between subject and evidence, and reason's purpose undocumented.

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 title states a specific verb+resource ('Submit a useful outcome claim') and the first sentence names the inputs supplied (subject/result revisions, actual contributors), so an agent can infer a write operation creating an outcome claim. However, the description uses undefined domain jargon ('beneficiary', 'outcome claim', 'verified credit') without grounding it, and gives no signal for how this differs from siblings like get_outcome, appeal_outcome, or review_outcome.

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?

Nothing tells the agent when to submit versus when to fetch (get_outcome), challenge (appeal_outcome), or evaluate (review_outcome). There is an implicit qualifier that self-use and unverified independence earn zero credit, but no explicit condition or workflow placement for choosing this tool over alternatives.

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