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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write nature is already known. The description adds genuinely useful context beyond annotations: this action locks funds on-chain with a cap of min(price/2, 50 USDC), signalling an irreversible financial commitment with a bounded amount. However it does not say what happens to the stake afterward (slashable, refundable, when released) or what state the intent moves to.

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?

A single front-loaded sentence with no filler: the action and the key numeric constraint arrive immediately. Its brevity is efficient, though it borders on under-specification given the 0% schema coverage.

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 money-locking mutation with three undocumented parameters and no output schema, the description should state required inputs, the resulting intent state, and eligibility conditions. None of that is present, leaving significant gaps an agent must resolve by guessing.

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%, so the description carries the full burden for three parameters, yet it names none of them explicitly. 'Their stake' loosely implies sellerStakeUsdc and the cap formula helps, but it does not explain that sellerStakeUsdc is optional, nor what agentId or intentId reference.

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 and resource ('accepts an intent') plus the concrete side effect ('locks their stake'), which tells an agent this is a staking commitment rather than a plain claim. It does not differentiate from close siblings such as accept_deal or claim_intent, so an agent cannot fully disambiguate from the description alone.

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 'Class B seller' implies the caller role, but there is no explicit when-to-use guidance: no precondition that the intent must be open, no statement of who is eligible, and no comparison to accept_deal or claim_intent, which are the obvious alternatives. Usage must be inferred entirely.

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