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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false), so the bar is lower. The description adds real behavioral context beyond them: validation including acceptance tests, immediate open status, the funded-wallet requirement, and the escrow timing at award acceptance.

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?

Two tight sentences with no filler, and the most decision-relevant fact (fixed-price task, immediate open) is front-loaded. Efficient for the size of the description.

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?

This is a high-complexity creation tool with 20 parameters, nested budget and acceptance_tests objects, and no output schema, yet the description is two sentences and covers almost none of the field semantics or the distinction from sibling creation tools.

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 35% across 20 parameters with nested objects, so the description is expected to compensate. Instead it mentions no parameters at all beyond a passing reference to acceptance tests and "fixed-price", leaving the vast majority of fields undocumented in both places.

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+resource ("Post a fixed-price task") and adds scope about validation and immediate opening. It does not differentiate from the close sibling post_enrichment_task, and "fixed-price" is mildly at odds with the schema's pricing_model enum which also allows fixed_bid.

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?

Gives useful operational context (needs a funded wallet, escrow occurs at accept-award) but never says when to choose this over post_enrichment_task or repost_task, nor any prerequisites beyond wallet funding. Usage is implied rather than stated.

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