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

With no annotations, the description carries the full burden and does disclose the crucial behavioral consequence: results enter quarantine for 'Humanity Loop verification' and cannot alter canonical state or trigger external actions. It omits auth requirements (node_token), idempotency/duplicate-submit behavior, and error modes, so it is strong but not complete.

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 tight sentences with the action front-loaded and the safety consequence immediately following. No filler text.

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 no annotations and no output schema, the description covers the workflow semantics (quarantine, no state change) but leaves the parameter surface almost entirely unexplained. It is adequate to understand the tool's role, insufficient to invoke it well.

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, so the description must compensate and largely fails. Only 'result'/'work_id' are loosely implied by 'task result'; node_token, evidence, uncertainty, and failure_modes receive no explanation at all.

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 Tier-0 task result'), which clearly separates it from siblings like contributor_register, contributor_checkin, and contributor_set_status. It does not name a sibling or draw an explicit boundary, but the purpose is unmistakable.

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?

The phrase 'a claimed Tier-0 task result' implies the prerequisite that a task must already be claimed, giving implied usage context. However, there is no explicit when-to-use vs alternatives guidance or statement about what to do if no task is claimed.

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