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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered and the description is free to add domain behavior — which it does at length: the payout formula (points x epoch point price), removal of cherry_reward, the distinction between review_target_hours (house target) and review_stats (measured median with sample size), and the reobserve payment/debt rules. What it does not disclose is browse-side behavior such as ordering, pagination beyond the limit default, or what 'progress' represents, which keeps it below a 5.

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 core purpose is buried inside a multi-level parenthetical, making the text hard to parse and poorly front-loaded despite opening with the verb. Substantial space is spent on reobserve economics and debt penalties that are the concern of task_claim and task_submit_proof rather than this browse tool, so not every sentence earns its place here.

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?

With no output schema, the description usefully compensates by describing the returned fields, which is the right instinct for a browse tool. However it omits the semantics of the filter parameters' interaction, pagination/ordering behavior, and any mention of what statuses are valid, while over-investing in one category's submission rules.

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 100%, so the baseline is 3 and every parameter (limit, status, symbol, category, exchange) is already documented in the schema. The description's added detail concerns output fields and the 'reobserve' category value, which largely duplicates the schema's own example, so it adds little parameter-level meaning beyond what structured data provides.

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 opening clause gives a concrete verb and resource ('Browse open Task Market tasks') and enumerates the returned fields (id, category, points value, progress, payout), so the agent knows precisely what comes back. It falls short of a 5 because the purpose statement is embedded in a long parenthesized run-on and sibling differentiation is only implied through the mention of task_claim/task_submit_proof as follow-ups rather than as alternatives to this tool.

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 routes the agent through a 'reobserve' workflow (claim via task_claim, submit via task_submit_proof), which is useful downstream context but not guidance about when to use tasks_browse itself. There is no statement such as 'call this first to find a task to claim' and no advice on which filters to use for which goal, so usage is only implied.

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