Search TaskMarket tasks

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It says 'Read-only, no wallet needed, cannot spend anything,' which covers the key safety aspect. However, it does not describe pagination, rate limits, or return format, leaving some behavioral details undisclosed.

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 two sentences with no filler. The first sentence states the core function, and the second adds relevant usage context. Every phrase 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?

Given the tool's complexity (10 parameters, no output schema, no annotations), the description is too sparse. It covers purpose and safety but omits filtering guidance, pagination behavior, and return value information, leaving significant gaps for effective usage.

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 10% (minReward), and the tool description provides no parameter details. With 10 parameters, including filters like mode, status, tags, and sort, the description fails to help users understand how to construct a valid query, so it doesn't compensate for the 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 uses a specific verb ('browse') and names the resource ('TaskMarket work'), clearly distinguishing it from the sibling create_task. It also states that the tool is read-only and non-spending, which further clarifies its role.

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?

It explicitly advises using this tool before create_task to evaluate whether delegating to a human/agent worker market is a better fit, giving a concrete usage scenario. It also includes prerequisites like 'no wallet needed' and 'cannot spend anything,' but does not mention alternative search tools or when not to use it.

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