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

With no annotations, the description carries the full burden, and it does disclose genuinely useful lifecycle behavior: submissions enter Humanity Loop review before becoming canonical state, and Tier-1 actions need receipts. It omits other important traits such as authentication via node_token, idempotency/resubmission behavior, and what happens to a failed submission.

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 with the action front-loaded and each sentence carrying a distinct payload (purpose, receipt requirement, review gate). Mild jargon ('Tier-1', 'Humanity Loop') costs a point but nothing is padded.

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 6-parameter mutation tool with a nested object, no annotations, and no output schema, the description is thin. It never explains how node_token is obtained, what the result object must contain, or what the caller receives after review, leaving the agent unable to call it confidently.

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% across 6 parameters, including a nested result object, so the description must compensate and largely does not. It touches evidence, uncertainty, and implicitly result and receipt, but leaves node_token, work_id, and failure_modes entirely undefined in either place.

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?

States a specific verb ('Submit') and resource ('a claimed contributor task result'), and adds the key qualifiers evidence and uncertainty. It does not, however, distinguish itself from the sibling contributor_* tools (checkin, register, set_status), so an agent must infer the boundary rather than read it.

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?

Usage is only implied: an agent infers it is called after claiming a task and before review. The one explicit conditional ('Tier-1 external actions should include a verifiable receipt') gives partial content guidance, but there is no statement of when not to use it or which sibling to prefer for adjacent operations.

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