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

With no annotations, the description carries the full burden, and it does add one genuine behavioral fact beyond the schema: no deposit is taken until an offer is accepted. It still omits the auth model the required wallet/nonce/signature parameters imply, and says nothing about whether a posted task can be cancelled or edited.

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 core action first and the differentiating constraint second. Every clause earns its place and nothing is padded.

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 mutation tool with no annotations and no output schema, one sentence is thin. It omits the nonce/signature auth flow, the currency and dispute_mode choices, and how the task connects to the make_offer/accept_offer siblings.

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 only 38% across 8 parameters, and the description explains none of them. It gives no meaning for title, spec, deadline, currency, or dispute_mode, so it does not compensate for the undocumented half of 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 and resource ('Post a task open for offers') and the parenthetical 'no price yet' implicitly separates it from the sibling post_task, which presumably carries a fixed price. The distinction is inferable rather than stated, so it stops short of a 5.

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?

'No price yet, no deposit until you accept an offer' gives implied usage context: use this when you want competitive offers instead of a fixed price. However, it never names post_task as the alternative or states the condition that selects between them, leaving routing to inference.

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