task_browse

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

With no annotations provided, the description carries the full burden. It usefully discloses return fields and the key detail that reward is already divided by 1e6. It does not mention pagination behavior or explicitly confirm read-only use, but the verb 'browse' implies a safe read operation.

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, front-loaded with the primary purpose, then efficiently covers return value details and filter options. No wasted words.

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 8 parameters, no output schema, and no annotations, the description adequately covers the core purpose, return fields, and available filters. It omits pagination/cursor behavior and default limits, but these are secondary for a browse tool and partially inferable from the schema.

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?

The schema covers 100% of parameters with descriptions, so the baseline is 3. The description only paraphrases the filter parameters (modes, tags, reward range) and adds no new syntax or format details beyond what the schema already includes. The USDC division detail pertains to return values, not parameters.

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 'Browse open Taskmarket tasks', a specific verb and resource, and lists the return fields (task ID, title, reward, status, submission count, deadline). This clearly distinguishes it from sibling tools like task_get (retrieve one task) and task_create (create a task).

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 clearly implies this tool is for browsing/listing tasks, with filtering by mode, tags, and reward range. However, it does not explicitly state when not to use it or name alternative tools (e.g., 'use task_get for a single task'), so it lacks explicit exclusion guidance.

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