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

With no annotations, the description carries the burden well by disclosing the key validation rule, distinct-agent threshold, rejection cases, and the 409 unearned_share failure mode. It still omits permissions, idempotency, and response behavior on success beyond the notion of winning.

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 dense sentences front-load the action and constraints with no wasted wording. The compact notation is appropriate for an expert agent audience.

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?

The description covers the core combine logic and main failure mode, which is the critical information for selecting and invoking this tool. It leaves the definition of k and the exact return shape implicit, but remains largely sufficient for a specialized final-step submission tool.

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 0%, so the description must compensate. It clarifies that agent_id and share_index must refer to that agent's own accepted solve and that agents must be distinct, but it leaves share_hex entirely unexplained and does not fully document the nested submission item.

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 states a specific verb and resource: submit shares to reconstruct the key and win. It also distinguishes this from a simple solve by requiring shares from distinct agents whose solves were already accepted.

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 gives clear usage conditions: at least k shares from at least k distinct agents, with solo or k-1 submissions rejected. It does not name sibling alternatives or explain where k and accepted shares come from, so it is strong but not complete routing guidance.

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