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

No annotations are provided, so the description carries the full burden. It discloses the pay-per-call cost ($0.001 USDC), the exact payment scheme (x402 v2, EIP-3009), and that malformed arguments aren't charged — valuable operational context. However, it does not describe the output format (e.g., array of tasks, pagination, order) or any rate limits. For a listing tool this is a notable omission, though the payment details are well covered.

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 concise and purpose-first: it states what the tool lists, then the commercial terms. It's not overly verbose, and every sentence provides useful information (purpose, payment cost, payment workflow). However, the payment details are somewhat dense and could be slightly streamlined, but overall it's well-structured for an agent to parse quickly.

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?

The tool is a paid list operation with one optional parameter and no output schema. The description covers the core usage (listing tasks, payment mechanics, cost), which is sufficient for an agent to decide and attempt a call. It lacks an explicit description of the response structure (e.g., array of task objects, fields), but the first sentence implies the return fields. Given the simplicity and the clear payment protocol, completeness is strong, though not exhaustive.

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 100%: the sole 'payment' parameter has a clear description explaining it's a base64 X-PAYMENT header and that omitting it returns terms. The description adds the payment scheme context (x402, USDC) beyond the schema, but this is supplementary rather than essential for understanding the parameter. Baseline 3 is appropriate since the schema already documents the parameter adequately.

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 states a specific verb ('List') and a concrete resource ('open TaskMarket tasks') with examples of what types (bounties/benchmarks/auctions) and what fields are returned (reward, mode, deadline, submission demand). This clearly distinguishes it from the siblings tm_get_task (single task) and tm_task_submissions (submissions). The purpose is unambiguous.

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 explains how to use the tool in terms of the payment flow: omit 'payment' to get terms, then pass the payment header to get data. It also states that every call requires a settled payment. It doesn't explicitly say 'use when you need to list tasks' vs alternatives, but the purpose is clear and the siblings are distinct enough that an agent can infer usage. The lack of explicit when-not-to-use is a minor gap.

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