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

With no annotations provided, the description carries the transparency burden. 'Browse' implies a read-only operation, and 'every open task is open to you' adds visibility semantics. Still, it does not disclose pagination behavior, response format, or how other statuses behave.

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 short sentences with no filler. The action is front-loaded, the status hint is targeted, and the final clause adds behavioral context about open-task accessibility.

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 definition is simple, but no output schema exists and the description does not mention what the response contains or how limit/offset pagination works. It gives a useful entry point for open tasks but leaves several operational details to inference.

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 0%, so the description must compensate. It adds meaning to the status parameter by recommending status='open' for finding work, but limit and offset receive no explanation beyond their self-evident names and defaults.

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 clearly identifies a task-browsing operation with the verb 'Browse' and resource 'tasks', and adds purpose through 'status="open" to find work'. It is distinguishable from sibling action tools like approve_task or get_task, though it does not explicitly name an alternative.

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 gives a concrete usage hint: use status='open' to find work, which is clear context. However, it does not explicitly contrast with alternatives like get_task, pick_task, or claim_task, nor does it state when not to use the tool.

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