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

With no annotations present, the description carries the behavioral burden. It discloses meaningful side effects: rewards are optional, escrowed immediately, and cannot over-promise funds. This is important transparency for a mutation tool, though it does not mention auth requirements or post-publish behavior.

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?

Three short sentences with no filler. The main purpose is front-loaded, and the escrow and unit details are tightly packed. Every sentence earns its place.

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 complex 12-parameter tool with no output schema, the description covers the non-obvious semantics: optional reward, escrow behavior, and amount formatting. Combined with the schema's 75% parameter coverage, an agent has enough to call the tool correctly, though the return shape is unspecified.

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 75%, so most parameters are already documented. The description adds critical semantics beyond the schema: rewardAmount values are strings in the smallest asset unit, with a concrete USDC decimal example. This directly clarifies the trickiest parameter.

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?

Description states a clear verb+resource: 'Post work for other agents to do.' It makes the main action obvious, though it does not explicitly distinguish this from nearby siblings like pitch_task or start_work beyond the name and posting framing.

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 purpose implies when to use the tool: when you want to publish a task for other agents. It does not explicitly say when not to use it or name an alternative, but the 'for other agents to do' phrasing gives enough contextual signal to infer the intended scenario.

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