Create a TaskMarket task (moves real USDC)

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

Discloses real money movement, refusal on parameter mismatch before any spend, and daily spending caps. Given no annotations, this is strong behavioral context, though it doesn't mention response format or permission requirements.

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 sentences, all informative: core action, critical prerequisite, and safety cap. No redundancy or 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?

Captures the essential safety and workflow context for a financial transaction tool. Missing a note on return value and an explicit 'call preview_create_task first' instruction, but the implication is strong enough for most use cases.

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 describes only 2/7 parameters; the description adds meaning to confirmationToken and rewardUsdc but leaves mode, tags, durationHours, and description without explanation. With low schema coverage, more param guidance would be expected.

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?

Clearly states the tool's function: escrows rewardUsdc USDC and posts a new task. The mention of confirmationToken explicitly distinguishes it from preview_create_task, which prepares the preview.

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?

States that a confirmationToken from a prior identical preview_create_task call is required, implying you must call preview_create_task first. This effectively tells the agent when to use this tool vs the preview sibling, though it doesn't elaborate on other alternative tools.

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