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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the write/safety profile is covered. The description adds real context beyond that: the one-proof-per-person-per-subject uniqueness rule and the fact that reobserve proof_data must validate against a fixed shape. It doesn't describe error behavior on rejected proofs, which holds it back from 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?

Three tight sentences, front-loaded with the core action before the conditional reobserve detail and the required-parameter note. Slightly indirect because the proof_data rules are delegated to another tool's description, forcing a lookup.

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 write tool with no output schema, the description covers the prerequisite, the required parameter's source, and the main validation constraint. Missing only what an agent might want on failure modes or what a successful submission returns.

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 100%, so the baseline is 3. The description goes further by naming claim_id's origin (task_claim) and flagging that proof_data validation depends on task category, with a pointer to tasks_browse for the reobserve shape. That cross-tool dependency is not in the 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?

States a specific verb (submit) and resource (proof for a claimed task), and situates it in the workflow by naming task_claim (source of claim_id) and tasks_browse (schema reference). An agent can distinguish it from task_claim and tasks_browse without opening a schema.

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?

Clear prerequisite is given: it applies to a task you've already claimed, and claim_id must come from task_claim. There is no explicit when-not guidance or statement of alternatives, but the workflow context is unambiguous.

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