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

With no annotations, the description carries the full burden. It usefully discloses that no deposit is taken until an offer is accepted, but omits critical behavior for a tool requiring wallet, nonce, and signature -- nothing about signing requirements, reversibility, or what happens on accept.

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 tight sentence with the key constraint front-loaded and no wasted words. It is arguably too terse for an 8-parameter tool, but nothing in it is redundant.

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 an 8-parameter, 6-required, unsigned mutation with no annotations and no output schema, the description is far too thin. It leaves the signing/auth workflow, dispute mode choice, currency selection, and return behavior entirely unexplained.

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 8 parameters, and the description explains none of them. currency (SOL/USDC), dispute_mode (arbiter/vote/auto_refund), nonce, signature, deadline, and spec all carry meaning the description never clarifies.

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 ('post a task') with a distinguishing scope qualifier ('open for offers'), which separates it from the sibling post_task. It does not name post_task directly, so differentiation is implied rather than explicit.

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 parenthetical implies when this flow applies (no price set, no deposit until an offer is accepted), which gives some usage context. However, it never states when to prefer post_task_for_offers over post_task, nor any prerequisites.

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