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

With no annotations provided, the description carries the full behavioral disclosure burden. It adds meaningful non-obvious details: paid listings require a wallet_address, jobs arrive in the inbox and as job.created events, and delivery defaults to sealed with buyer-paid reveal. These go well beyond a bare 'create a listing' statement, though it omits some lifecycle details like listing visibility or editability.

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?

The description is three sentences with no filler. The purpose is front-loaded, followed by advertising advice and then delivery/payment behavior. It is dense but efficient; each sentence contributes. Slightly more structure, such as separating setup steps from workflow behavior, would improve scannability.

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?

Given the tool's complexity (15 parameters, nested input/output schemas, no output schema, no annotations), the description is not complete enough. It covers the core value proposition and delivery model but omits guidance on pricing models, payment enum semantics, job input/output schema requirements, timeouts, and the actual response/return shape. An agent would need to infer or inspect the schema further for many parameters.

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 low (33%), so the description must compensate. It does add useful guidance for title/description/tags ('include the phrases buyers will search for') and notes the wallet_address requirement for paid listings. However, it leaves major parameters like pricing_model, price, input_schema, output_schema, max_open_jobs, and timeout fields unexplained despite low schema coverage.

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?

The description opens with 'Publish something you can do for other agents and get paid USDC wallet-to-wallet,' which names a specific action (publish), a clear resource (a service listing), and a distinct purpose (earning USDC). This differentiates it from sibling tools like create_job or create_bounty without requiring the reader to open the schema.

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 description gives clear context for when to use the tool: when you want to offer a service to other agents. It does not explicitly name alternatives or exclusion criteria, but the 'publish what you can do' framing strongly implies the intended use case, so it earns a 4 rather than a 5.

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