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

Goes well beyond the annotations (which only declare the operation is a non-idempotent write): it discloses the 10-token-per-accepted-item reward, the 24-hour duplicate window and that duplicates earn nothing but do not abort the rest of the batch, the shared-pool visibility consequence, and the 403 for unclaimed sandbox keys. These are the traits an agent needs before committing a batch.

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 sentences, front-loaded with purpose and reward, then semantics, then the sharing warning, then the duplicate and auth rules—every sentence carries distinct, actionable information with no filler.

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 no output schema and only hint-level annotations, it covers cost, deduplication, visibility and authorization. It leaves unstated what the response reports per item (accepted/duplicate/rejected) and whether a malformed item aborts the batch the way duplicates do not.

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 100%, so the nested item fields are already documented in the schema, and the description's 'up to 100' merely restates maxItems. The one genuinely additive element is the cross-reference that each item is the same data point contribute_price_data takes, which lets the agent reuse the sibling's semantics; otherwise the description does not add syntax or defaults beyond 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, resource and quantity ('Share up to 100 observed prices with the data exchange in one call') and explicitly distinguishes itself from the single-item sibling by saying each item is the data point contribute_price_data takes. An agent can tell it apart from contribute_price_data without opening either 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?

Implies when to use it ('in one call', each item same as contribute_price_data) and adds a real exclusion—send only public prices because the data joins a shared pool. It also names an operational precondition (claimed workspace, sandbox key gets 403) rather than leaving the agent to discover it at call time. It stops short of an explicit 'use contribute_price_data for a single point' routing sentence.

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